Bug #36199 Master failure during master_lcp can lead to node failure
Submitted: 18 Apr 2008 9:04 Modified: 31 May 2008 10:46
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:* OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[18 Apr 2008 9:04] Jonas Oreland
Found while trying to retest issue.

How to repeat:

Suggested fix:
[23 Apr 2008 14:07] 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:


ChangeSet@1.2600, 2008-04-23 16:08:38+02:00, jonas@perch.ndb.mysql.com +7 -0
  ndb -
    fix for bug#36199, bug#36246, bug#36247, bug#36276
    all related to cascading master failure
[25 Apr 2008 7:57] Jonas Oreland
pushed to 51-ndb, telco* and drop6
(50-ndb was locked for unknown reason)
[20 May 2008 9:34] Jon Stephens
Documented in the 5.1.24-ndb-6.3.14 changelog as follows:

        Under certain rare circumstances, the failure of the new master node
        while attempting a node takeover would cause takeover errors to repeat
        without being resolved.

Left Patch Queued status pending further merges.
[31 May 2008 10:46] Jon Stephens
Closed following discussion with Jonas.
[12 Dec 2008 23:25] Bugs System
Pushed into 6.0.6-alpha  (revid:sp1r-jonas@perch.ndb.mysql.com-20080423140838-48946) (version source revid:jonas@mysql.com-20080808094047-4e1yiarqa2t3opg3) (pib:5)