Bug #43109 ndbmtd can't handle multi-nodefailure

Submitted:	23 Feb 2009 14:04	Modified:	23 Feb 2009 16:26
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:
When 2 nodes dies simultaneous, LocalProxy gets confused when counting NF_COMPLETE_REP

This causes the surviving nodes to die aswell

How to repeat:
run testcase for bug#43108
observe that 2 original nodes also die.

Suggested fix:
fix counting

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

2884 Jonas Oreland	2009-02-23
      ndb - bug#43109 - fix counting of NF_COMPLETE_REP

Pushed into 5.1.32-ndb-6.4.4 (revid:jonas@mysql.com-20090223150851-2fu4yfdw3ojc8u7x) (version source revid:jonas@mysql.com-20090223140503-xv75q7hmmd4m2hl5) (merge vers: 5.1.32-ndb-6.4.3) (pib:6)

Documented bugfix in the NDB-6.4.4 changelog as follows:

        When using ndbmtd, multiple data node failures
        caused the remaining data nodes to fail as well.

Page generated in 0.052 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.