一次mysql slave故障的解决过程

最新推荐文章于 2023-07-03 22:30:00 发布

原创

最新推荐文章于 2023-07-03 22:30:00 发布 · 9.1k 阅读

2 ·

CC 4.0 BY-SA版权

文章标签：

#mysql

本文记录了一次MySQL slave由于网络问题导致relay log损坏的故障解决过程，包括检查错误日志、停止slave、更改master信息、重置及重启slave等步骤，最终成功恢复slave的正常运行。

mysql> show slave status\G
Last_SQL_Error: 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. Error_code: 1594
看样子，应该由于网络原因 slave relay log损坏了

查看 mysql 日志：
170306 12:34:08 [Note] Slave SQL thread initialized, starting replication in log ‘mysql-bin.000033’ at position 77270703, relay log ‘./HK3ASERVER-relay-bin.066281’ position: 10604437
170306 12:34:08 [ERROR] Error in Log_event::read_log_event(): ‘read error’, data_len: 67, event_type: 19
170306 12:34:08 [ERROR] Error reading relay log event: slave