MySQL Bugs: #19020: Failure of one cluster storage node can cascade into failure of another storage

Bug #19020	Failure of one cluster storage node can cascade into failure of another storage
Submitted:	11 Apr 2006 18:40	Modified:	12 Apr 2006 11:41
Reporter:	David Dawe	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	5.0.19 (max)	OS:	Sparc Solaris 10
Assigned to:	Assigned Account	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

Extracted from output log file

Attachment: ndb_4_out.log (application/octet-stream, text), 1.59 KiB.

Extracted from error log file

Attachment: ndb_4_error.log (application/octet-stream, text), 393 bytes.

Compressed trace log

Attachment: ndb_4_trace.log.11.bz2 (application/octet-stream, text), 25.92 KiB.