MySQL Bugs: #18043: Reboot cause node failure on other server in cluster

Bug #18043	Reboot cause node failure on other server in cluster
Submitted:	7 Mar 2006 17:22	Modified:	19 Jun 2006 9:52
Reporter:	Andrew Harrison	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	5.0.18	OS:	Linux (SLES 9 SP1)
Assigned to:		CPU Architecture:	Any

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

Trace log for node that caused the rest of the nodes to fail

Attachment: ndb_8_trace.log.zip (application/zip, text), 78.49 KiB.

Cluster log from the Server that was not rebooted.

Attachment: ndb_2_cluster.zip (application/x-zip-compressed, text), 59.15 KiB.

Cluster log

Attachment: ndb_1_cluster.zip (application/x-zip-compressed, text), 33.01 KiB.