Bug #27203 ScanDelete+Scan+Insert could cause node crash
Submitted: 16 Mar 2007 9:54 Modified: 23 Mar 2007 8:50
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1 OS:
Assigned to: Jonas Oreland CPU Architecture:Any

[16 Mar 2007 9:54] Jonas Oreland
testScan -l 1000 -n InsertDelete T1

How to repeat:
testScan -l 1000 -n InsertDelete T1
[16 Mar 2007 9:59] 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:


ChangeSet@1.2438, 2007-03-16 10:58:24+01:00, jonas@perch.ndb.mysql.com +2 -0
  ndb - bug#27203
    Allow readTablePk to stumble on scan+deleted tuple,
        reporting no-match instead of crash (in case scan is lock-owner)
[22 Mar 2007 20:44] Mads Martin Joergensen
Fixed in 5.1.17
[23 Mar 2007 8:50] 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


Documented bugfix in 5.1.17 and mysql-5.1.15-ndb-6.1.6 changelogs.