Bug #26758 SLAVE Replication SQL Thread Crashes DataNode(s)
Submitted: 1 Mar 2007 17:16 Modified: 4 Jun 2007 8:37
Reporter: Steve Edwards Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.1.16 OS:Linux (Debian Linux 64bit)
Assigned to: Guangbao Ni CPU Architecture:Any
Tags: cluster, Error: 2341 datamemory index, replication, sql thread

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:

[6 Mar 2007 9:05] Steve Edwards
Trace files from crashed Slave cluster data node

Attachment: ndb_error_trace.tar.gz (application/x-gzip, text), 391.85 KiB.

[6 Mar 2007 9:16] Steve Edwards
Slave cluster increase in Datamemory during replication.

Attachment: slave_cluster_datamemory.jpg (image/jpeg, text), 151.03 KiB.

[8 Mar 2007 14:28] Steve Edwards
replication mysqld debug trace update row

Attachment: cluster_repli_update_row.trace (application/octet-stream, text), 34.25 KiB.

[16 Mar 2007 15:29] Steve Edwards
mysqld slave replication trace file - call to last_uniq_key removed - update correctly performed as replace

Attachment: update_row_postfix.trace (application/octet-stream, text), 16.16 KiB.