MySQL GTID模式下跳过多个错误

本文介绍了在MySQL的GTID模式下如何跳过复制错误,包括单个和多个错误的处理方法。针对单个错误,通过分析从库报错信息,解析主库binlog并跳过错误。在非多线程复制环境下,可以使用pt-slave-restart工具,而在多线程复制环境下,可以通过自定义脚本来跳过错误。
摘要由CSDN通过智能技术生成

MySQL跳过复制错误

1. GTID模式下跳过单个复制错误

(1)分析从库报错信息

mysql> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 172.21.167.73
                  Master_User: Repl
                  Master_Port: 20201
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000001
          Read_Master_Log_Pos: 1083
               Relay_Log_File: mysql-relay-bin.000002
                Relay_Log_Pos: 971
        Relay_Master_Log_File: mysql-bin.000001
             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: 1062
                   Last_Error: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 1 failed executing transaction 'eef85c8f-bef5-11eb-a336-00e0ed90dfcb:4' at master log mysql-bin.000001, end_log_pos 1052. See error log and/or performance_schema.replication_applier_status_by_worker table for more details about this failure or others, if any.
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 805
              Relay_Log_Space: 1456
              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: 1062
               Last_SQL_Error: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 1 failed executing transaction 'eef85c8f-bef5-11eb-a336-00e0ed90dfcb:4' at master log mysql-bin.000001, end_log_pos 1052. See error log and/or performance_schema.replication_applier_status_by_worker table for more details about this failure or others, if any.
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 16773
                  Master_UUID: eef85c8f-bef5-11eb-a336-00e0ed90dfcb
             Master_Info_File: mysql.slave_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: 210527 22:24:43
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: eef85c8f-bef5-11eb-a336-00e0ed90dfcb:1-4
            Executed_Gtid_Set: eef85c8f-bef5-11eb-a336-00e0ed90dfcb:1-3
                Auto_Position: 0
         Replicate_Rewrite_DB: 
                 Channel_Name: 
           Master_TLS_Version: 


    Retrieved_Gtid_Set 是slave接收到的事务的信息,Executed_Gtid_Set是slave已经执行的master的信息,意味着复制的时候从库遇到主库的事务eef85c8f-bef5-11eb-a336-00e0ed90dfcb:4发生了错误,理论上跳过 eef85c8f-bef5-11eb-a336-00e0ed90dfcb:4 就可以的。
    
	1)对于直接提示GTID的,可通过如下流程跳过:
mysql> stop slave;  
mysql> set gtid_next='eef85c8f-bef5-11eb-a3
  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

Zhi@Li

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值