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
You have to follow below steps to troubleshoot the error.
Execute the below command
SHOW MASTER STATUS
SHOW SLAVE STATUS
Check the error log for replication and its position.
Ideally there are three sets of file/position coordinates in SHOW SLAVE STATUS to identify the correct file
1) The position, ON THE MASTER, from which the I/O thread is reading: Master_Log_File/Read_Master_Log_Pos.
2) The position, IN THE RELAY LOGS, at which the SQL thread is executing: Relay_Log_File/Relay_Log_Pos
3) The position, ON THE MASTER, at which the SQL thread is executing: Relay_Master_Log_File/Exec_Master_Log_Pos
Next you have to check the error log for the log position to identify the correct binary log file and set the correct log file using below command.
CHANGE MASTER TO MASTER_LOG_FILE=’mysql-bin.000480′
Once the problem is resolved you can use Maatkit tool to sync table to multiple slaves.
mk-table-checksum command is used to check what tables are out of sync and when use mk-table-sync command is used to resync them.