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:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1	OS:
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
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:

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:

  http://lists.mysql.com/commits/10116

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"

pushed to 5.1.12

Documented incompatible change in 5.1.12 changelog, Cluster Upgrades/Downgrades seciton of Manual.

Page generated in 0.038 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.