Bug #24917 | Makeing node restart with "newly" dropped disk table can cause failure during re | ||
---|---|---|---|
Submitted: | 8 Dec 2006 16:20 | Modified: | 28 Dec 2006 14:08 |
Reporter: | Jonas Oreland | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Disk Data | Severity: | S3 (Non-critical) |
Version: | 5.1 | OS: | |
Assigned to: | Jonas Oreland | CPU Architecture: | Any |
[8 Dec 2006 16:20]
Jonas Oreland
[8 Dec 2006 16:22]
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/16671 ChangeSet@1.2351, 2006-12-08 17:21:29+01:00, jonas@perch.ndb.mysql.com +1 -0 ndb - bug#24917
[28 Dec 2006 14:08]
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 fix in 5.1.15 changelog.