Bug #14028 [Data Loss] NDB node crashes during backup if a BLOB is inserted and deleted
Submitted: 14 Oct 2005 13:51 Modified: 14 Mar 2006 8:55
Reporter: eric von Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:4.1.15, 5.0.18 OS:Linux (SuSE 9.2)
Assigned to: Jonas Oreland 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:

[5 Dec 2005 16:22] eric von
Cluster log from this weekend and prior.  Note the frequent crashes at backup time (4:15AM UTC)

Attachment: ndb_1_cluster.maskedips.zip (application/zip, text), 28.70 KiB.

[5 Dec 2005 22:20] eric von
"Successful" split-brain cluster crash on 4.1.15, including ndb_mgm show output post-crash.

Attachment: 4.1.15-crashlogs.tgz (application/x-compressed, text), 16.51 KiB.

[7 Dec 2005 15:31] eric von
Traces generated on NDB2 during backup crashes in 4.1.15

Attachment: NDB2.zip (application/zip, text), 168.78 KiB.

[7 Dec 2005 15:31] eric von
Traces generated on NDB3 during backup crashes in 4.1.15

Attachment: NDB3.zip (application/zip, text), 110.22 KiB.

[7 Dec 2005 15:31] eric von
Traces generated on NDB4 during backup crashes in 4.1.15

Attachment: NDB4.zip (application/zip, text), 167.95 KiB.

[7 Dec 2005 15:32] eric von
Cluster log during and after backup crashes in 4.1.15

Attachment: ndb_1_cluster.zip (application/zip, text), 36.27 KiB.

[23 Feb 2006 22:50] eric von
Crash trace from node 4, and relevant portion of cluster log.  Nodes 2 and 3 did not generate traces.

Attachment: node4crash.zip (application/zip, text), 40.05 KiB.