Bug #21478 Incorrect logpart after "noderestart --initial" followed by noderestart
Submitted: 7 Aug 2006 12:12 Modified: 1 Sep 2006 16:18
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

[7 Aug 2006 12:12] Jonas Oreland
Do noderestart --initial, followed by a node restart

The result will be that there will be incorrect logpart assigned to fragments
  so ndbd will die while reading redo log

NOTE TO JON: The fix for this will make it impossible to do any online-upgrade
  only ndb backup/mysqldump possible

How to repeat:

Suggested fix:
[7 Aug 2006 12:33] 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.2264, 2006-08-07 14:32:43+02:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#21478
    make fragment logpart in DIH "global"
[1 Sep 2006 8:04] Jonas Oreland
pushed to 5.1.12
[1 Sep 2006 16:18] Jon Stephens
Documented incompatible change in 5.1.12 changelog, Cluster Upgrades/Downgrades seciton of Manual.