Bug #23430 | Node failure in testOperations / DeleteUpdate with new table | ||
---|---|---|---|
Submitted: | 18 Oct 2006 15:58 | Modified: | 4 Dec 2006 4:39 |
Reporter: | Kristian Nielsen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Disk Data | Severity: | S3 (Non-critical) |
Version: | 5.1.13 | OS: | Linux (Linux) |
Assigned to: | Jonas Oreland | CPU Architecture: | Any |
[18 Oct 2006 15:58]
Kristian Nielsen
[18 Oct 2006 18:42]
Jonas Oreland
this is fairly newly introduced...maybe by pekka's abort fixes... anyway, logspace got freed twice, making accounting for logfile group corrupt
[18 Oct 2006 18:43]
Jonas Oreland
also, reproducable with D1 or D2
[18 Oct 2006 18:54]
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/13908 ChangeSet@1.2308, 2006-10-18 20:54:25+02:00, jonas@perch.ndb.mysql.com +1 -0 ndb - bug#23430 make sure not to release log buffer twice (or several times) in case of abort of multi update
[20 Oct 2006 12:21]
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/14054 ChangeSet@1.2304, 2006-10-20 14:21:30+02:00, jonas@perch.ndb.mysql.com +1 -0 ndb - bug#23430 make sure not to release log buffer twice (or several times) in case of abort of multi update
[25 Oct 2006 6:59]
Jonas Oreland
pushed into 5.1-ndb
[1 Nov 2006 14:57]
Jonas Oreland
pushed into 5.1.13
[1 Dec 2006 8:40]
Jonas Oreland
The error was the "log buffer" for DD was incorrectly handled (space was freed twice on abort, during some circumstances) This would cause direct assertion if debug build and slow and mysterious death in release build
[4 Dec 2006 4:39]
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 for 5.1.13.