Contents
How to fix MySQL relay Master log corrupted?
To fix the error, current binlog files on slave should be discarded and set new position. Before setting new binlog position it’s important to remember Relay_Master_Log_File and Exec_Master_Log_Pos values from corrupted slave server using command SHOW SLAVE STATUS \\G:
What to do if the slave relay log has errors?
If the slave relay log has errors, run the following commands to reset the slave and corrupted logs reconnect to the master, get the ok logs and start slaving again.
What should I do with my relay log?
Therefore, the solution was to discard current relay binlogs and to point slave to the last master binlog position. Here is complete output from show slave status\\G on stopped slave server:
How to check the Master’s binary log or relay log?
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.
How to fix MySQL replication after slaves relay log was?
Here is complete output from show slave status\\G on stopped slave server: Last_Error: Relay log read failure: Could not parse relay log event entry. master’s or slave’s MySQL code. If you want to check the master’s by issuing ‘SHOW SLAVE STATUS’ on this slave. To fix the error, current binlog files on slave should be discarded and set new position.
Is there a way to skip the relay log?
But with “gtid_mode=ON” and “relay_log_recovery = 1”, the relay log files will be discard later, and so, at the beginning should skip the relay log read. workaround: The following steps can start slave successfully reset slave; start slave IO_THREAD; stop slave IO_THREAD; reset slave; start slave;
Can a reset slave delete Master relay log?
Just to note that “reset slave” will delete master.info, relay-log.info and all the relay log files, so it’s not needed to clean leftovers in /var/lib/mysql directory. After all commands were executed, slave has reconnected to the master and start to read SQL statements (Seconds_Behind_Master value was not NULL any more).