現象：
mysql> show slave status\G;
*************************** 1. row ***************************
-------------------------------------------------
              Master_Log_File: mysql-bin.000191
          Read_Master_Log_Pos: 334164088
               Relay_Log_File: mysql-srelay.000533
                Relay_Log_Pos: 902042386
        Relay_Master_Log_File: mysql-bin.000190
             Slave_IO_Running: Yes
            Slave_SQL_Running: No
  Replicate_Wild_Ignore_Table:
                   Last_Errno: 1594
                   Last_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_log如下：
160519 18:42:21 [ERROR] Error reading relay log event: Could not open log file
160519 18:42:21 [ERROR] Slave SQL: 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 abl
e to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 1594
160519 18:42:21 [ERROR] Slave (additional info): File '/data/mysql3307/logs/mysql-srelay.030613' not found (Errcode: 2) Error_code: 29
160519 18:42:21 [Warning] Slave: File '/data/mysql3307/logs/mysql-srelay.030613' not found (Errcode: 2) Error_code: 29
160519 18:42:21 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.009095' position 1069989357

解析：

從日誌我們看出可能是master或者slave的binlog損壞或者網路問題
但是網路測過是正常的
然後stop slave，發現主庫上的binlog繼續增加，且沒產生error_log
由此懷疑從庫中繼binlog損害

解決：
既然找出了原因，解決就相對容易了
1.從庫執行reset slave，清除掉binlog日誌
2.從出錯前的位置開始啟動複製
本例的複製位置為：
'mysql-bin.009095' position 1069989357

【MySQL】複製1594錯誤（從庫relaylog損壞）

相關文章