MySQL Bugs: #18118: Master node shutdown caused full cluster crash

Bug #18118	Master node shutdown caused full cluster crash
Submitted:	9 Mar 2006 23:21	Modified:	27 Mar 2006 15:30
Reporter:	Adam Dixon (Candidate Quality Contributor)
Status:	Closed
Category:	Server: Cluster	Severity:	S2 (Serious)
Version:	4.1, 5.0, 5.1	OS:	Linux (RHEL4)
Assigned to:	Jonas Oreland	Target Version:

Description:
I have a 8 NDBD node (8machines) 2replica setup. Each node with 6gb memory.
I proceeded to go from nodeid 18 through to 11;
X stop (and wait for it to stop)
X# ndbd (and wait for it to start)
Where X is 18, 17, 16, 15, 14, 13, 12, 11*
*11: This was the last node (and was 'Master' in 'show' output.), and triggered the full
crash.

See http://lists.mysql.com/cluster/3273 for Jonas Oreland's comment.

How to repeat:
See above, It may have something to do with query load on the cluster, or the amount of
data in a running cluster.

The problem is that the master takeover prints so much in cluster log
so that sendbuffer gets full...

solution: timeslice or decrease printouts

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:

  http://lists.mysql.com/commits/3993

pushed into 5.1.8

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:

  http://lists.mysql.com/commits/4125

pushed into 5.0.20

pushed into 4.1.19

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
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in 4.1.19, 5.0.20, 5.1.8 changelogs. Closed.