Bug #2011 rare race condition producing "binlog has bad magic number" error in slave
Submitted: 4 Dec 2003 7:10 Modified: 4 Dec 2003 7:34
Reporter: Guilhem Bichot
Status: Closed
Category:Server: Replication Severity:S3 (Non-critical)
Version:4.0.16 OS:Any (all)
Assigned to: Guilhem Bichot Target Version:

[4 Dec 2003 7:10] Guilhem Bichot 
Description:
This causes a rare failure of the rpl_max_relay_size.test test. Is present in 4.0.16,
4.1.1 and the 5.0 tree.

How to repeat:
The failure can be made repeatable by adding a sleep() before check_binlog_magic()
around line 3540 in sql/slave.cc, and then running the test.

Suggested fix:
will push a fix now.
[4 Dec 2003 7:12] Guilhem Bichot 
More precisely, the error says that the slave SQL thread could not use one of the relay
logs because it has a bad magic number.
[4 Dec 2003 7:34] Guilhem Bichot 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Fixed in the 4.0 tree:
ChangeSet@1.1640.1.1, 2003-12-04 15:30:14+01:00, guilhem@mysql.com