MySQL Bugs: #18385: partial restart failure after create table

Bug #18385	partial restart failure after create table
Submitted:	21 Mar 2006 9:33	Modified:	27 Mar 2006 13:54
Reporter:	Tomas Ulin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	4.1,5.0,5.1	OS:
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
start 2 node cluster
create table
insert a few rows
stop node 2
stop cluster
partial restart using node 2
=> unable to find restorable replica
 

How to repeat:
./mysql-test-run --do-test=ndb --start-and-exit
create table t1 (a int key) engine=ndb;
insert into t1 values(1),(2),(3),(4);

ndb_mgm>  2 stop
ndb_mgm>  all stop

cd var/ndbcluster-9350
../../../storage/ndb/src/kernel/ndbd -c "nodeid=2;localhost:9350"

Time: Tuesday 21 Mars 2006 - 11:16:13
Status: Ndbd file system error, restart node initial
Message: Unable to find a restorable replica (Ndbd file system inconsistency error, please report a bug)
Error: 6303
Error data: table: 0 fragment: 0 gci: 100
Error object: DBDIH (Line: 9084) 0x0000000a
Program: ../../../storage/ndb/src/kernel/ndbd
Pid: 26499
Trace: ./ndb_2_trace.log.1
Version: Version 5.1.8 (beta)
***EOM***

2006-03-21 13:12:18 [MgmSrvr] INFO     -- Node 2: Started (version 5.1.8)
...
no local check point reported to have started
...
2006-03-21 13:13:32 [MgmSrvr] INFO     -- Node 2: Node shutdown completed.
...
2006-03-21 13:14:39 [MgmSrvr] INFO     -- Node 3: Node 2 Connected
...
2006-03-21 13:16:13 [MgmSrvr] ALERT    -- Node 2: Forced node shutdown completed. Occured during startphase 4. Initiated by signal 6. Caused by error 630
3: 'Unable to find a restorable replica(Ndbd file system inconsistency error, please report a bug). Ndbd file system error, restart node initial

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

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

pushed for 2-node cluser into 5.1.8

pushed into 5.0.20

pushed into 4.1.19

The fix that has been pushed does only work for 2-node clusters.
To handle bigger cluster, we need "graceful stop nodes" which stops 
  a bunch of nodes within same GCI.

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 bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix with note of current limitation in 4.1.19, 5.0.20, and 5.1.8 changelogs. Bug report closed.