Bug #48436 Incorrect handling of redo-intervals after node-failure during node-restart

Submitted:	30 Oct 2009 13:47	Modified:	30 Oct 2009 19:06
Reporter:	Jonas Oreland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	mysql-5.1-telco-6.2	OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
Randomly
1) starting node
2) crashing node during restart
3) system restart

could lead to incorrect handling of meta-data for REDO log,
causing "Error while reading REDO log" to happen during the system restart

How to repeat:
testNodeRestart -n NFDuringRestart long enough
or my new test-prg

Suggested fix:
keep meta-data correct!

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/88748

3147 Jonas Oreland	2009-10-30
      ndb - bug#48436 - cleanup of crashedreplica handling in dih

pushed 6.3.29 and 7.0.10

Documented bugfix in the NDB.7.0.10 changelog as follows:

        A data node crashing while restarting, followed by a system
        restart could lead to incorrect handling of redo log metadata,
        causing the system restart to fail with Error while reading 
        REDO log.

Closed.

Page generated in 0.053 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.