GTID跳过事务

1.错误原因是因为从库误删数据,再删的主库数据,导致从库找不到主库删除的那条数据

复制代码
             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: 1032
                   Last_Error: Could not execute Delete_rows event on table xp.xp; Can't find record in 'xp', Error_code: 1032; handler error HA_ERR_END_OF_FILE; the event's master log test4-bin.000003, end_log_pos 2342

2.跳过事务

复制代码
mysql>  select * from performance_schema.replication_applier_status_by_worker\G
*************************** 1. row ***************************
                                           CHANNEL_NAME:
                                              WORKER_ID: 0
                                              THREAD_ID: NULL
                                          SERVICE_STATE: OFF
                                      LAST_ERROR_NUMBER: 1032
                                     LAST_ERROR_MESSAGE: Could not execute Delete_rows event on table xp.xp; Can't find record in 'xp', Error_code: 1032; handler error HA_ERR_END_OF_FILE; the event's master log test4-bin.000003, end_log_pos 2342
                                   LAST_ERROR_TIMESTAMP: 2023-11-24 14:46:35.916545
                               LAST_APPLIED_TRANSACTION: b0610c84-8a92-11ee-be7e-2a26553b6ba7:11
     LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2023-11-24 14:45:41.094280
    LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2023-11-24 14:45:41.094280
         LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2023-11-24 14:45:40.661198
           LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2023-11-24 14:45:40.663848
                                   APPLYING_TRANSACTION: b0610c84-8a92-11ee-be7e-2a26553b6ba7:12
         APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2023-11-24 14:46:36.348964
        APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2023-11-24 14:46:36.348964
             APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 2023-11-24 14:46:35.916135
                 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0
   LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0
  LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE:
LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000
                     APPLYING_TRANSACTION_RETRIES_COUNT: 0
       APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0
      APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE:
    APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000
1 row in set (0.00 sec)


其中   APPLYING_TRANSACTION: b0610c84-8a92-11ee-be7e-2a26553b6ba7:12  就是我们要跳过的事务

3.跳过事务

复制代码
mysql> set gtid_next='b0610c84-8a92-11ee-be7e-2a26553b6ba7:12';
Query OK, 0 rows affected (0.00 sec)

mysql> begin; commit;    ## 设置空事件,如果不设置,会重启slave时会报错
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

mysql> set session gtid_next = automatic;  ##重新获取gtid的事件
Query OK, 0 rows affected (0.00 sec)

mysql> start slave;
Query OK, 0 rows affected (0.00 sec)

4.再次查看

复制代码
	mysql> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 
                  Master_User: slave
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: test4-bin.000003
          Read_Master_Log_Pos: 196
               Relay_Log_File: test1-relay-bin.000004
                Relay_Log_Pos: 411
        Relay_Master_Log_File: test4-bin.000003
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
相关推荐
叼烟扛炮3 分钟前
Linux 学习笔记(三十八):从实模式到分页——处理器内存管理的发展史
linux·运维·服务器
ClouGence7 分钟前
SQL 效率天花板!开源 CloudDM,自带一站式 AI SQL 助手
数据库·sql·开源
润滑卫士19 分钟前
油液水分在线传感器技术对比:电容法、电阻法与微波法的测量原理与适用性
运维
Decay__19 分钟前
附-01 · MySQL 压测与容量规划 —— sysbench 基准测试、容量评估与参数基线
运维·数据库·sql·mysql·架构
这个DBA有点耶24 分钟前
主从切换报成功,业务却写不进去——数据层脑裂与应用层连接残留的两类假成功
数据库·架构·dba
qq_4523962324 分钟前
第八篇:《VACUUM、自动清理与膨胀治理》
jvm·数据库·oracle
SelectDB技术团队34 分钟前
ClickHouse 支持存算分离吗?Doris 社区版原生存算分离怎么落地
数据库·clickhouse·云原生·开源·apache doris·技术选型·存算分层
mennekes37 分钟前
暗装插座箱 VS 明装插座箱,工地和车间怎么取舍
运维·网络·科技·安全·制造
叼烟扛炮38 分钟前
Linux 学习笔记(三十六):并发进阶——读写锁 vs 自旋锁,到底怎么选?
linux·运维·服务器·笔记·学习
DBA_G40 分钟前
南大通用GBase 8a数据库可视化灾备解决工具GVR
数据库