MySQL複製錯誤：Relay log read failure - Could not parse relay log event entry

MySQL複製報錯，錯誤提示：

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.

解決辦法：

show slave status\G

輸出如下：

Slave_IO_State: Waiting for master to send event
                  Master_Host: *
                  Master_User: rpl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000080
          Read_Master_Log_Pos: 464278824
               Relay_Log_File: backup-relay-bin.000241
                Relay_Log_Pos: 229883280
        Relay_Master_Log_File: mysql-bin.000075
             Slave_IO_Running: Yes
            Slave_SQL_Running: No
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  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&nbsp
;check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW&nb
sp;SLAVE STATUS' on this slave.
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 229883067
              Relay_Log_Space: 5510894579
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 1594
               Last_SQL_Error: Relay log read failure: Could not parse relay log event&nbsp
;entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog'&nbs
p;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&nbsp
;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.
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: 5c5dd7f6-2a37-11ec-ba0f-82a8aca001f9
             Master_Info_File: /www/server/data/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: 
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 220415 01:07:54
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: 
            Executed_Gtid_Set: 
                Auto_Position: 0
         Replicate_Rewrite_DB: 
                 Channel_Name: 
           Master_TLS_Version:

記下這兩個欄位的值：Relay_Master_Log_File 和 Exec_Master_Log_Pos

執行如下命令重置 、重啟slave：

STOP SLAVE;

RESET SLAVE;

CHANGE MASTER TO master_log_file='mysql-bin.000075', master_log_pos=229883067;

START SLAVE;

重新觀察slave狀態，發現恢復正常~

show slave status\G;