Bug #48143 ndb_mgmd - crash in CONFIG_CHECK_REF
Submitted: 19 Oct 2009 9:22 Modified: 2 Nov 2009 15:39
Reporter: Magnus Blåudd Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:7.0.9 OS:Any
Assigned to: Magnus Blåudd CPU Architecture:Any

[19 Oct 2009 9:22] Magnus Blåudd
Description:
The CONFIG_CHECK that each ndb_mgmd run to check that all connected ndbd_mgmd's have the same configuration may fail with an assert if a configuration change occurs while the check is ongoing. A configuration change is allowed to take place during the check and the check should simply be scheduled to be run again at a later time when the configuration change has completed.

How to repeat:
testMgmd

Suggested fix:
Drop the CONFIG_CHECK_REF and thus cause the check to be run again later.
[19 Oct 2009 12:07] Magnus Blåudd
Pushed to 7.0
[2 Nov 2009 15:39] Jon Stephens
Documented bugfix in the NDB-7.0.10 changelog as follows:

        The configuration check that each management server runs to
        verify that all connected ndbd_mgmd processes have the same
        configuration could fail when a configuration change took place
        while this check was in progress. Now in such cases, the
        configuration check is rescheduled for a later time, after the
        change is complete.

Closed.