Bug #54611 Unnessesary REDO execution during system/node-restart
Submitted: 18 Jun 2010 10:15 Modified: 10 Jul 2010 6:36
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.3 OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[18 Jun 2010 10:15] Jonas Oreland
When a system/node shutdown directly after a LCP, 
it can happen that this LCP is not used to restore cluster.

The problem is that one comparison in restart code is
made using "<" instead of "<="

Problem should be harmless.

Found by code-inspection.

How to repeat:
run new testcase

Suggested fix:
Fix comparison
[18 Jun 2010 10:50] 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:


3221 Jonas Oreland	2010-06-18
      ndb - bug#54611 - fix so that latest completed LCP is used even if cluster shutsdown directly afterwards
[18 Jun 2010 11:03] Bugs System
Pushed into 5.1.47-ndb-7.0.16 (revid:jonas@mysql.com-20100618105702-99j9v9ng0zxj338f) (version source revid:jonas@mysql.com-20100618105702-99j9v9ng0zxj338f) (merge vers: 5.1.47-ndb-7.0.16) (pib:16)
[18 Jun 2010 11:04] Jonas Oreland
pushed to 6.3.35, 7.0.16 and 7.1.5
[10 Jul 2010 6:36] Jon Stephens
Documented in the NDB-6.3.35, 7.0.16, and 7.1.5 changelogs, as follows:

        If a node shutdown (either in isolation or as part of a system
        shutdown) occurred directly following a local checkpoint, it was
        possible that this local checkpoint would not be used when
        restoring the cluster.