Bug #15530 Cluster start up "show" shows all data nodes as master during start
Submitted: 6 Dec 2005 16:48 Modified: 20 Apr 2006 6:20
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1.26, 5.0.20, 5.1.2 OS:Linux (Linux)
Assigned to: Stewart Smith CPU Architecture:Any

[6 Dec 2005 16:48] Jonathan Miller
While starting cluster all data nodes show group 0 and to be master:

[ndbd(NDB)]     6 node(s)
id=4    @  (Version: 5.1.2, starting, Nodegroup: 0, Master)
id=5    @  (Version: 5.1.2, starting, Nodegroup: 0, Master)
id=6    @  (Version: 5.1.2, starting, Nodegroup: 0, Master)
id=7    @  (Version: 5.1.2, starting, Nodegroup: 538673559, Master)
id=8    @  (Version: 5.1.2, starting, Nodegroup: 268910684, Master)
id=9    @  (Version: 5.1.2, starting, Nodegroup: 538673559, Master)

How to repeat:
start cluster

Suggested fix:
not to shopw any as master until master is actually selected
[6 Apr 2006 14:56] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[7 Apr 2006 2:54] Stewart Smith
tomas and jonas think this is okay.

The bug seems to be caused by a race condition on when we're querying for information versus what we're sending.

If you waited a bit longer before typing show, it shouldn't have been a problem (or had faster hardware and network). This is probably why it's hard to reproduce on a single machine (fast network :)

Together with the fix for BUG#18843, this bug should be fixed. Please reopen if you see it after these patches have gotten through as if you do, it means my theory is wrong :)
[19 Apr 2006 7:45] Stewart Smith
pushed to 5.0.21 and 5.1.10
[20 Apr 2006 6:20] Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Documented fix in 5.0.21 and 5.1.10 changelogs; closed.