Bug #32519 LCP starts before previous LCP is restorable (wrt GCP)
Submitted: 20 Nov 2007 13:31 Modified: 15 Dec 2007 9:24
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:* OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[20 Nov 2007 13:31] Jonas Oreland
seen by testSystemRestart -n SR_DD_1_LCP T1
(and causes crash when running with only 2 LCP's)

How to repeat:
testSystemRestart -n SR_DD_1_LCP T1
[20 Nov 2007 14:09] 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.2581, 2007-11-20 15:08:48+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#32519
    Add *correct* check when a LCP is restorable
    by looking at maxGciStarted from LCP_FRAG_REP
    (for all fragments)
    bug observed by running testSystemRestart -n SR_DD_1_LCP T1
    (causes "incorrect" behaviour in 51-ndb, and crash when using 2 LCP)
[20 Nov 2007 17:34] Jonas Oreland
pushed to 51-ndb, telco-62, telco-63 and 51-telco
havent decided about drop6
[23 Nov 2007 10:49] Jon Stephens
Documented bugfix in 5.1.22-ndb-6.2.9 changelog. Left status as PQ.
[14 Dec 2007 17:08] Bugs System
Pushed into 5.1.23-rc
[14 Dec 2007 17:09] Bugs System
Pushed into 6.0.5-alpha
[15 Dec 2007 9:24] 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


Bugfix also now documented in the 5.1.23 and 6.0.5 changelogs; closed.