Hi,
Yes, quite likely that you hit on a bug.
The error message below is a common place where bugs in the
system restart phase will end up so it doesn't say more than that
there is an inconsistency in the recovery data on disk.
You can always try to do a system restart with only the node last working
at first and then when starting up the problematic one do that with a node
restart using initial to get rid of the problematic inconsistencies. This might
work dependent on what's gone wrong.
Rgrds Mikael
Chris Kennedy wrote:
> I have a 2 node cluster, 2 replicas. I have one
> simple table (8 byte numberic key, and a 2 byte
> numeric data field). I was attempting to load up
> 33,000,000 rows (the config.ini file had the
> memory setting as:
>
> DataMemory= 3000M
> IndexMemory=1400M
> )
>
> When in the region of 31,000,000 rows were loaded,
> it would not take any more. I increased the
> DataMemory to 3200M, stopped and restarted the
> management node, and then selected one of the
> datanodes and restarted it. After it had
> restarted, I attempted to do likewise with the
> other data node, but it failed with:
>
> 2002: Stop failed
> Node shutdown would cause system crash.
>
> I shutdown the cluster, and attempted to restart
> it, which failed:
>
> 2005-11-23 09:51:12 ALERT -- Node 3: Forced
> node shutdown completed. Occured during startphase
> 4. Initiated by signal 0. Caused by error 2310:
> 'Error while reading the REDO log(Ndbd file system
> inconsistency error, please report a bug). Ndbd
> file system error, restart node initial'.
>
> Is there any way I can recover from this without
> reloading all my data? Is this a known bug?
>
> Platform:
> 2 HP Proliant DL585 servers:
> 4x Dual Core 2.2GHz Opteron CPU s
> 16GB RAM
> RHEL4 AS 64bit
>
> MySQL release:
> mysql-max-5.0.15-linux-x86_64-glibc23.tar.gz
Mikael Ronstrom
Senior Software Architect, MySQL AB
My blog:
http://mikaelronstrom.blogspot.com