| Bug #14028 | [Data Loss] NDB node crashes during backup if a BLOB is inserted and deleted | ||
|---|---|---|---|
| Submitted: | 14 Oct 2005 15:51 | Modified: | 14 Mar 2006 9:55 |
| Reporter: | eric von | ||
| Status: | Closed | ||
| Category: | Server: Cluster | Severity: | S1 (Critical) |
| Version: | 4.1.15, 5.0.18 | OS: | Linux (SuSE 9.2) |
| Assigned to: | Jonas Oreland | Target Version: | |
If the data you need to attach is more than 500KB, you should create
a compressed archive of the data and a README file that describes the data
with a filename that includes the bug number (example:
bug-data-14028.zip), and use FTP to upload the archive
to ftp://ftp.mysql.com/pub/mysql/upload/.
Once you have uploaded the file, add a comment to this bug to notify us about
it. Note: This directory is unlistable, which means that once you
have uploaded your file, you will not be able to see it.
All entries become the exclusive editorial property of Sun Microsystems, Inc.
"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.
Traces generated on NDB2 during backup crashes in 4.1.15
Attachment: NDB2.zip (application/zip, text), 168.78 KiB.
Traces generated on NDB3 during backup crashes in 4.1.15
Attachment: NDB3.zip (application/zip, text), 110.22 KiB.
Traces generated on NDB4 during backup crashes in 4.1.15
Attachment: NDB4.zip (application/zip, text), 167.95 KiB.
Cluster log during and after backup crashes in 4.1.15
Attachment: ndb_1_cluster.zip (application/zip, text), 36.27 KiB.
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.
