MySQL Forums
Forum List  »  MySQL Administrator

Replication Failed / Master binlog corruption
Posted by: Andrey Padiy
Date: December 24, 2010 05:05AM


Has anyone experienced this or can help figure out what happened?

We have a master and 3 slaves with ROW based replication. One slave replicates all databases and the other two only replicate a few databases/tables.
Two days ago all of the slaves crashed at the same time and all reported the following on SHOW SLAVE STATUS :

" Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. "

I noted the master relay log file and position on one of the slaves and on the master run :

db1:/opt# mysqlbinlog --start-position 27819298 mysqld-bin.001780
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
# at 4
#101222 14:34:51 server id 93 end_log_pos 106 Start: binlog v 4, server v 5.1.34-log created 101222 14:34:51
# Warning: this binlog is either in use or was not closed properly.
ERROR: Error in Log_event::read_log_event(): 'Event too big', data_len: 1397506381, event_type: 58
# End of log file
ROLLBACK /* added by mysqlbinlog */;

And there are many of these in the same binlogfile :

ERROR: Error in Log_event::read_log_event(): 'Event too big', data_len: XXXXXX, event_type: XX

We have upgraded mysql to 5.1.54 since and rebuilt replication from scratch but still have the old file to debug.

What's concerning is this :

Event too big', data_len: 1397506381

Does this mean someone was running a 1.3GB query?

Many thanks.

P.S We were running Mysql 5.1.34 on Linux Debian 5 x64.

Edited 2 time(s). Last edit at 12/24/2010 05:08AM by Andrey Padiy.

Options: ReplyQuote

Written By
Replication Failed / Master binlog corruption
December 24, 2010 05:05AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.