Bug #41089 Cluster Crash with error Forced node shutdown completed. Caused by error 2303
Submitted: 28 Nov 2008 11:29 Modified: 11 Jan 2009 13:23
Reporter: Shueb Khan Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.0.41 OS:Linux
Assigned to: CPU Architecture:Any
Tags: Cluster crash with error Forced node shutdown completed. Caused by error 2303

[28 Nov 2008 11:29] Shueb Khan 
Description:
Our database cluster crashed yesterday with the errors as below.
At that time, a user script was running on the database. After the Cluster was started again, the script was re-run from where it got disconnected, and it completed without error.
Could you please help us understand what might have caused this crash.
I have attached the log files related to it.

Thanks very much.

"2008-11-26 12:19:27 [MgmSrvr] ALERT    -- Node 3: Forced node shutdown completed. Caused by error 2303: 'System error, node killed during node restart by other node(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'."

and 

"Time: Wednesday 26 November 2008 - 12:19:25
Status: Temporary error, restart node
Message: System error, node killed during node restart by other node (Internal error, programming error or missing error message, pl
ease report a bug)
Error: 2303
Error data: Please report this as a bug. Provide as much info as possible, expecially all the ndb_*_out.log files, Thanks. Shutting down node due to failed handling of GCP_SAVEREQ
Error object: DBLQH (Line: 18735) 0x0000000a "

How to repeat:
Not tried repeating
[28 Nov 2008 11:38] Shueb Khan 
As the log files are greater than 500k, they have been uploaded to 
ftp://ftp.mysql.com/pub/mysql/upload/

The file name is Logs_Bug #41089.zip
[11 Dec 2008 13:23] Martin Skold 
Has this bug been verified on newer versions?
Try ndb-6.2 for example.
[12 Jan 2009 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".