Bug #34260 Rare race condition between aborted insert + scan delete can cause node crash
Submitted: 3 Feb 2008 12:59 Modified: 20 Feb 2008 21: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:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[3 Feb 2008 12:59] Jonas Oreland
Two scans can que up on a insert that gets aborted
In this case the assert(nextSerial == RNIL) is incorrect

How to repeat:
testDict -n TableAddAttrsDuring T1 T2 T7

Suggested fix:
remove assertion
[3 Feb 2008 13:01] 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.2534, 2008-02-03 14:01:31+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#34260
    remove incorrect ndbrequire
[10 Feb 2008 12:09] Jonas Oreland
pushed to 51-ndb, telco-6.x (>=2)
[12 Feb 2008 15:16] Jon Stephens
Documented in the 5.1.23-ndb-6.3.9 changelog as follows:

      In certain rare circumstances, a race condition could occur
      between an aborted insert and a delete leading a data node crash.

Left in PQ status pending additional merges.
[12 Feb 2008 16:10] Jon Stephens
Also documented for 5.1.23-ndb-6.2.12.
[20 Feb 2008 16:03] Bugs System
Pushed into 5.1.24-rc
[20 Feb 2008 16:03] Bugs System
Pushed into 6.0.5-alpha
[20 Feb 2008 21:50] Jon Stephens
Also documented for 5.1.24 and 6.0.5.