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:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	*	OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
Found while trying to retest issue.

How to repeat:
.

Suggested fix:
.

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/45894

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

pushed to 51-ndb, telco* and drop6
(50-ndb was locked for unknown reason)

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.

Closed following discussion with Jonas.

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)

Page generated in 0.058 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.