MySQL Bugs: #29232: Replication not usable because of corrupted slave relay logs

Bug #29232	Replication not usable because of corrupted slave relay logs
Submitted:	20 Jun 2007 8:49	Modified:	27 Mar 2008 17:29
Reporter:	Stef Cant	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	Server version: 5.0.42 Gentoo Linux	OS:	Linux (Gentoo Linux)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	corrupt relay, replication

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

slave status after failure

Attachment: show_slave_status.txt (text/plain), 2.29 KiB.

part of the master bin log file

Attachment: mysqlbinlog_master_firefoot-bin.000010.txt (text/plain), 25.09 KiB.

part of the slave relay log file

Attachment: mysqlbinlog_slave_relay-strider.000022.txt (text/plain), 6.48 KiB.

my thoughts about what happened

Attachment: investigation_faulty_query.txt (text/plain), 2.85 KiB.

output of 'show slave status'

Attachment: 2_show_slave_status.txt (text/plain), 2.29 KiB.

part of mysqlbinlog (master )

Attachment: 2_mysqlbinlog_master_firefoot-bin.000008.txt (text/plain), 48.79 KiB.

part of mysqlbinlog (slave)

Attachment: 2_mysqlbinlog_slave_relay-strider.000018.txt (text/plain), 22.68 KiB.

3 relevant queries

Attachment: 2_investigation_faulty_query.txt (text/plain), 2.46 KiB.