Bug #21536 Partial start rolling back GCI can lead to subsequent failures during node resta

Submitted:	9 Aug 2006 12:13	Modified:	6 Sep 2006 11:16
Reporter:	Jonas Oreland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	4.1, 5.0, 5.1	OS:
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
 

How to repeat:
  

Suggested fix:

start 2 node cluster
shutdown node 2
start node 2 -n
error insert 10000
start node 2
wait for 2 to fail
stop node 1
start node 2 --no-waitnodes=1
start node 1 --initial
crash

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

ChangeSet@1.2542, 2006-08-09 16:24:14+02:00, jonas@perch.ndb.mysql.com +3 -0
  ndb - bug#21536
    Make sure updateNodeInfo is run on master also for temporary tables

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

ChangeSet@1.2041, 2006-08-31 11:56:45+02:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#21536
      Make sure updateNodeInfo is run on master also for temporary tables

pushed to 5.1.12

pushed to 5.0.25

pushed into 4.1.22

Documented bugfix in 4.1.22/5.0.25/5.1.12 changelogs.

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