Bug #22013 ndb_mgmd can get confused by node shutdown, makeing event reporting broken
Submitted: 5 Sep 2006 11:58 Modified: 25 Jan 2007 4:19
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.0-> OS:
Assigned to: Jonas Oreland CPU Architecture:Any

[5 Sep 2006 11:58] Jonas Oreland 
Description:
start mysqld
start node
stop node just before first apiregconf has been sent to ndb_mgmd
start node again, and ndb_mgmd will not handle this correctly wrt event reporting

How to repeat:
 

Suggested fix:
[5 Sep 2006 12:00] 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/11391

ChangeSet@1.2043, 2006-09-05 14:00:12+02:00, jonas@perch.ndb.mysql.com +4 -0
  ndb - bug#22013
    Fix bug in event handling wrt early node shutdown
[23 Jan 2007 4:50] 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/18598
[24 Jan 2007 1:59] Tomas Ulin 
pushed to 5.1.15
[24 Jan 2007 7:51] Tomas Ulin 
pushed to 5.0.36
[25 Jan 2007 4:19] 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.36 and 5.1.15 changelogs.