Bug #46412 | NDBRequire hit in Dbdih::invalidateLcpInfoAfterSr | ||
---|---|---|---|
Submitted: | 27 Jul 2009 18:02 | Modified: | 18 Aug 2009 15:03 |
Reporter: | Andrew Hutchings | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | 6.3.24 | OS: | Any |
Assigned to: | Jonas Oreland | CPU Architecture: | Any |
[27 Jul 2009 18:02]
Andrew Hutchings
[10 Aug 2009 13:43]
Martin Skold
Does restarting the node manually (possibly with --inital) solve the problem?
[10 Aug 2009 15:14]
Andrew Hutchings
The cluster was restored from backup before --initial was tried and the problem could not be reproduced since.
[17 Aug 2009 13:16]
Jonas Oreland
reproduced...using 2 new error inserts
[18 Aug 2009 6:57]
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: http://lists.mysql.com/commits/80966 3010 Jonas Oreland 2009-08-18 ndb - bug#46412 Fix/handle incorrectly set lcp-bits during system restart
[18 Aug 2009 7:02]
Jonas Oreland
pushed to 6.3.26 and 7.0.7 docs: 1) lcp starts 2) master dies almost directly afterwards 3) rest of cluster dies within 1-2s 4) crash when restarting
[18 Aug 2009 15:03]
Jon Stephens
Documented bugfix in the NDB-6.3.26 and 7.0.7 changelogs as follows: Killing MySQL Cluster nodes immediately following a local checkpoint could lead to a crash of the cluster when later attempting to perform a system restart. The exact sequence of events causing this issue was as follows: 1. Local checkpoint occurs. 2. Immediately following the LCP, kill the master data node. 3. Kill the remaining data nodes within a few seconds of killing the master. 4. Attempt to restart the cluster.