• mysql主从同步错误


    一、主从同步报错
    mysql> show slave statusG;
    *************************** 1. row ***************************
                   Slave_IO_State: Waiting for master to send event
                      Master_Host: 192.168.12.128
                      Master_User: repl
                      Master_Port: 3306
                    Connect_Retry: 60
                  Master_Log_File: mysql-bin.000003
              Read_Master_Log_Pos: 471
                   Relay_Log_File: node02-relay-bin.000005
                    Relay_Log_Pos: 411
            Relay_Master_Log_File: mysql-bin.000003
                 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 test.test; Can't find record in 'test', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log mysql-bin.000003, end_log_pos 440
                     Skip_Counter: 0
              Exec_Master_Log_Pos: 196
                  Relay_Log_Space: 936
                  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: 1032
                   Last_SQL_Error: Could not execute Delete_rows event on table test.test; Can't find record in 'test', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log mysql-bin.000003, end_log_pos 440
      Replicate_Ignore_Server_Ids:
                 Master_Server_Id: 1
                      Master_UUID: 201aff26-1857-11eb-adaf-00505625b4dc
                 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: 201104 19:05:32
                   Master_SSL_Crl:
               Master_SSL_Crlpath:
               Retrieved_Gtid_Set: 201aff26-1857-11eb-adaf-00505625b4dc:10-11
                Executed_Gtid_Set: 201aff26-1857-11eb-adaf-00505625b4dc:1-10,
    9c6c32db-187e-11eb-846e-005056229b2b:1-141
                    Auto_Position: 1
             Replicate_Rewrite_DB:
                     Channel_Name:
               Master_TLS_Version:
           Master_public_key_path:
            Get_master_public_key: 0
                Network_Namespace:
    1 row in set, 1 warning (0.01 sec)
    
    
    原因:主库要删除的数据在从库对应的表上找不到。
    
    
    解决步骤:
    --- 通过 Last_SQL_Errno 报错编号查询具体的报错事务
    mysql> select * from performance_schema.replication_applier_status_by_worker where LAST_ERROR_NUMBER=1032G;
    *************************** 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 test.test; Can't find record in 'test', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log mysql-bin.000003, end_log_pos 440
                                       LAST_ERROR_TIMESTAMP: 2020-11-04 19:05:32.900750
                                   LAST_APPLIED_TRANSACTION:
         LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
        LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
             LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000
               LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000
                                       APPLYING_TRANSACTION: 201aff26-1857-11eb-adaf-00505625b4dc:11
             APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2020-11-04 19:05:33.232725
            APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2020-11-04 19:05:33.232725
                 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 2020-11-04 19:05:32.898866
                     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.01 sec)
    
    ERROR:
    No query specified
    
    --- 停止主从复制
    mysql> stop slave;
    Query OK, 0 rows affected, 1 warning (0.00 sec)
    
    --- 跳过查找到报错的事务( APPLYING_TRANSACTION的值)
    mysql> set @@session.gtid_next='201aff26-1857-11eb-adaf-00505625b4dc:11';
    Query OK, 0 rows affected (0.00 sec)
    
    --- 提交一个空的事务,因为设置gtid_next后,gtid的生命周期开始了,必须通过显性的提交一个事务来结束;
    mysql> begin;
    Query OK, 0 rows affected (0.00 sec)
    
    mysql> commit;
    Query OK, 0 rows affected (0.00 sec)
    
    --- 改回自动模式;
    mysql> set @@session.gtid_next=automatic;
    Query OK, 0 rows affected (0.00 sec)
    
    --- 重启主从复制
    mysql> start slave;
    Query OK, 0 rows affected, 1 warning (0.01 sec)
    
    mysql> show slave statusG;
    *************************** 1. row ***************************
                   Slave_IO_State: Waiting for master to send event
                      Master_Host: 192.168.12.128
                      Master_User: repl
                      Master_Port: 3306
                    Connect_Retry: 60
                  Master_Log_File: mysql-bin.000003
              Read_Master_Log_Pos: 471
                   Relay_Log_File: node02-relay-bin.000006
                    Relay_Log_Pos: 458
            Relay_Master_Log_File: mysql-bin.000003
                 Slave_IO_Running: Yes
                Slave_SQL_Running: Yes
                  Replicate_Do_DB:
              Replicate_Ignore_DB:
               Replicate_Do_Table:
           Replicate_Ignore_Table:
          Replicate_Wild_Do_Table:
      Replicate_Wild_Ignore_Table:
                       Last_Errno: 0
                       Last_Error:
                     Skip_Counter: 0
              Exec_Master_Log_Pos: 471
                  Relay_Log_Space: 1198
                  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: 0
    Master_SSL_Verify_Server_Cert: No
                    Last_IO_Errno: 0
                    Last_IO_Error:
                   Last_SQL_Errno: 0
                   Last_SQL_Error:
      Replicate_Ignore_Server_Ids:
                 Master_Server_Id: 1
                      Master_UUID: 201aff26-1857-11eb-adaf-00505625b4dc
                 Master_Info_File: mysql.slave_master_info
                        SQL_Delay: 0
              SQL_Remaining_Delay: NULL
          Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
               Master_Retry_Count: 86400
                      Master_Bind:
          Last_IO_Error_Timestamp:
         Last_SQL_Error_Timestamp:
                   Master_SSL_Crl:
               Master_SSL_Crlpath:
               Retrieved_Gtid_Set: 201aff26-1857-11eb-adaf-00505625b4dc:10-11
                Executed_Gtid_Set: 201aff26-1857-11eb-adaf-00505625b4dc:1-11,
    9c6c32db-187e-11eb-846e-005056229b2b:1-141
                    Auto_Position: 1
             Replicate_Rewrite_DB:
                     Channel_Name:
               Master_TLS_Version:
           Master_public_key_path:
            Get_master_public_key: 0
                Network_Namespace:
    1 row in set, 1 warning (0.01 sec)
    
    
    二、主从同步报错
    mysql> show slave statusG;
    *************************** 1. row ***************************
                   Slave_IO_State: Waiting for master to send event
                      Master_Host: 192.168.12.128
                      Master_User: repl
                      Master_Port: 3306
                    Connect_Retry: 60
                  Master_Log_File: mysql-bin.000003
              Read_Master_Log_Pos: 746
                   Relay_Log_File: node02-relay-bin.000006
                    Relay_Log_Pos: 458
            Relay_Master_Log_File: mysql-bin.000003
                 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: Could not execute Write_rows event on table test.test; Duplicate entry '5' for key 'test.PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql-bin.000003, end_log_pos 715
                     Skip_Counter: 0
              Exec_Master_Log_Pos: 471
                  Relay_Log_Space: 1473
                  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: Could not execute Write_rows event on table test.test; Duplicate entry '5' for key 'test.PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql-bin.000003, end_log_pos 715
      Replicate_Ignore_Server_Ids:
                 Master_Server_Id: 1
                      Master_UUID: 201aff26-1857-11eb-adaf-00505625b4dc
                 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: 201104 19:21:46
                   Master_SSL_Crl:
               Master_SSL_Crlpath:
               Retrieved_Gtid_Set: 201aff26-1857-11eb-adaf-00505625b4dc:10-12
                Executed_Gtid_Set: 201aff26-1857-11eb-adaf-00505625b4dc:1-11,
    9c6c32db-187e-11eb-846e-005056229b2b:1-142
                    Auto_Position: 1
             Replicate_Rewrite_DB:
                     Channel_Name:
               Master_TLS_Version:
           Master_public_key_path:
            Get_master_public_key: 0
                Network_Namespace:
    1 row in set, 1 warning (0.01 sec)
    
    原因:主库在有唯一主键的表中插入的数据,在从库中已经存在,从库中出现主键冲突。
    
    解决方法:
    mysql> stop slave;
    Query OK, 0 rows affected, 1 warning (0.00 sec)
    
    mysql> select * from performance_schema.replication_applier_status_by_worker where LAST_ERROR_NUMBER=1062G;
    *************************** 1. row ***************************
                                               CHANNEL_NAME:
                                                  WORKER_ID: 0
                                                  THREAD_ID: NULL
                                              SERVICE_STATE: OFF
                                          LAST_ERROR_NUMBER: 1062
                                         LAST_ERROR_MESSAGE: Could not execute Write_rows event on table test.test; Duplicate entry '5' for key 'test.PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql-bin.000003, end_log_pos 715
                                       LAST_ERROR_TIMESTAMP: 2020-11-04 19:21:46.399334
                                   LAST_APPLIED_TRANSACTION:
         LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
        LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
             LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000
               LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000
                                       APPLYING_TRANSACTION: 201aff26-1857-11eb-adaf-00505625b4dc:12
             APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2020-11-04 19:21:46.733146
            APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2020-11-04 19:21:46.733146
                 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 2020-11-04 19:21:46.398725
                     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.01 sec)
    
    ERROR:
    No query specified
    
    mysql> set @@session.gtid_next='201aff26-1857-11eb-adaf-00505625b4dc:12';
    Query OK, 0 rows affected (0.00 sec)
    
    mysql> begin;
    Query OK, 0 rows affected (0.00 sec)
    
    mysql> commit;
    Query OK, 0 rows affected (0.00 sec)
    
    mysql> set @@session.gtid_next=automatic;
    Query OK, 0 rows affected (0.00 sec)
    
    mysql> start slave;
    Query OK, 0 rows affected, 1 warning (0.01 sec)
    
    mysql> show slave statusG;
    *************************** 1. row ***************************
                   Slave_IO_State: Waiting for master to send event
                      Master_Host: 192.168.12.128
                      Master_User: repl
                      Master_Port: 3306
                    Connect_Retry: 60
                  Master_Log_File: mysql-bin.000003
              Read_Master_Log_Pos: 746
                   Relay_Log_File: node02-relay-bin.000007
                    Relay_Log_Pos: 458
            Relay_Master_Log_File: mysql-bin.000003
                 Slave_IO_Running: Yes
                Slave_SQL_Running: Yes
                  Replicate_Do_DB:
              Replicate_Ignore_DB:
               Replicate_Do_Table:
           Replicate_Ignore_Table:
          Replicate_Wild_Do_Table:
      Replicate_Wild_Ignore_Table:
                       Last_Errno: 0
                       Last_Error:
                     Skip_Counter: 0
              Exec_Master_Log_Pos: 746
                  Relay_Log_Space: 1245
                  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: 0
    Master_SSL_Verify_Server_Cert: No
                    Last_IO_Errno: 0
                    Last_IO_Error:
                   Last_SQL_Errno: 0
                   Last_SQL_Error:
      Replicate_Ignore_Server_Ids:
                 Master_Server_Id: 1
                      Master_UUID: 201aff26-1857-11eb-adaf-00505625b4dc
                 Master_Info_File: mysql.slave_master_info
                        SQL_Delay: 0
              SQL_Remaining_Delay: NULL
          Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
               Master_Retry_Count: 86400
                      Master_Bind:
          Last_IO_Error_Timestamp:
         Last_SQL_Error_Timestamp:
                   Master_SSL_Crl:
               Master_SSL_Crlpath:
               Retrieved_Gtid_Set: 201aff26-1857-11eb-adaf-00505625b4dc:10-12
                Executed_Gtid_Set: 201aff26-1857-11eb-adaf-00505625b4dc:1-12,
    9c6c32db-187e-11eb-846e-005056229b2b:1-142
                    Auto_Position: 1
             Replicate_Rewrite_DB:
                     Channel_Name:
               Master_TLS_Version:
           Master_public_key_path:
            Get_master_public_key: 0
                Network_Namespace:
    1 row in set, 1 warning (0.01 sec)

    参考链接:
    https://blog.csdn.net/qq_35170079/article/details/83508621
    https://www.jb51.net/article/198062.htm

      

  • 相关阅读:
    二、JVM — 垃圾回收
    一、JVM — Java内存区域
    四、JVM — 类文件结构
    java 如何重写equal 和hashcode方法(最佳实践)
    Java关于继承中的内存分配
    Linux — 基础知识
    Zookeeper — 应用场景
    分布式服务接口请求的顺序性如何保证?
    如何设计一个高并发系统?
    索引策略
  • 原文地址:https://www.cnblogs.com/orcl-2018/p/13925979.html
Copyright © 2020-2023  润新知