Bug #29057 Incorrect handling of file 0 during redo execution(Error while reading REDO log)
Submitted: 12 Jun 2007 18:45 Modified: 4 Jul 2007 9:01
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1,5.0,5.1 OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[12 Jun 2007 18:45] Jonas Oreland
If a atleast 2 files are involved in REDO invalidation, 
  then file 0 - page 0, is not updated and points to invalid part of redo log

How to repeat:
run following against 1-node 5.1 cluster, with GCP set to 2s
(different numbers are needed for 4.1/5.0)

create_tab T1
hugoLoad -r 1000 T1
hugoScanUpdate -l 100 T1
ndb_mgm -e "all dump 7090 30000"
hugoScanUpdate -l 150 T1
ndb_mgm -e "all restart -a"
ndb_mgm -e "all restart -a"
ndb_mgm -e "all restart -a"

Suggested fix:
update file 0 page 0 after redo invalidation
[25 Jun 2007 5:13] 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.2497, 2007-06-25 07:12:27+02:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - post merge 50/51 - bug#29057 bug#29067 and bug#29118
[29 Jun 2007 17:10] Jon Stephens
Documented bugfix for telco-6.1.15 release, left status as PP.
[2 Jul 2007 12:51] Jonas Oreland
pushed to 50-ndb, drop5/6 51-ndb, 51-telco, telco-6.1
[3 Jul 2007 6:22] Jon Stephens
Also documented for telco-6.2.3 release.
[3 Jul 2007 18:57] Bugs System
Pushed into 5.1.21-beta
[4 Jul 2007 9:01] 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.21 changelog.
[10 Jul 2007 13:28] Bugs System
Pushed into 5.0.46