Bug #24752 Node failure during SchemaOp can cause subsequence node-failure
Submitted: 1 Dec 2006 13:56 Modified: 6 Dec 2006 12:35
Reporter: Jonas Oreland
Status: Closed
Category:Server: Cluster Severity:S3 (Non-critical)
Version:5.0, 5.1 OS:
Assigned to: Jonas Oreland Target Version:

[1 Dec 2006 13:56] Jonas Oreland 
Description:
Crash master node during create table
node state will be BS_NODEFAILURE

then when new node tries to start, new master will crash

How to repeat:
 

Suggested fix:
[1 Dec 2006 13: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/16300

ChangeSet@1.2276, 2006-12-01 13:57:29+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#24752
    This prevent any subsequent node restarts, but it's better than crashing an alive
node
[6 Dec 2006 12:35] Jon Stephens 
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 bug fix. More information about accessing the source trees is
available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.0.32 and 5.1.14 changelogs.