mysql从库误删数据后和gtid复制断开后怎么处置
发布时间：2021-12-29 00:23:40 所属栏目：MySql教程 来源：互联网
导读：这篇文章主要介绍了mysql从库误删数据后和gtid复制断开后怎么处理，具有一定借鉴价值，感兴趣的朋友可以参考下，希望大家阅读完这篇文章之后大有收获，下面让小编带着大家一起了解一下。 情景： 应该是主库上删数据，结果从库上先删了一下，然后主库再次删的
|
这篇文章主要介绍了mysql从库误删数据后和gtid复制断开后怎么处理，具有一定借鉴价值，感兴趣的朋友可以参考下，希望大家阅读完这篇文章之后大有收获，下面让小编带着大家一起了解一下。 情景： 应该是主库上删数据，结果从库上先删了一下，然后主库再次删的时候导致从库的同步断开 报错： root@xhh_test 01:58:58>SHOW SLAVE statusG *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: 10.13.28.52 Master_User: repl Master_Port: 3306 Connect_Retry: 60 Master_Log_File: binlog.000006 Read_Master_Log_Pos: 1375851 Relay_Log_File: relaylog.000012 Relay_Log_Pos: 1345735 Relay_Master_Log_File: binlog.000006 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: mysql.% Last_Errno: 1032 Last_Error: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 0 failed executing transaction 'a42e8e2b-886a-11e7-962b-00155d1cca18:121' at master log binlog.000006, end_log_pos 1345900. 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: 1345608 Relay_Log_Space: 1376222 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: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 0 failed executing transaction 'a42e8e2b-886a-11e7-962b-00155d1cca18:121' at master log binlog.000006, end_log_pos 1345900. 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: 523306 Master_UUID: a42e8e2b-886a-11e7-962b-00155d1cca18 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: 180224 13:56:50 Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: a42e8e2b-886a-11e7-962b-00155d1cca18:2-202 Executed_Gtid_Set: a42e8e2b-886a-11e7-962b-00155d1cca18:1-120, a5c5f6cf-886a-11e7-8494-00155d1cca17:1-259408, aa30ac69-886a-11e7-a031-00155d1cca1a:1-6 Auto_Position: 1 Replicate_Rewrite_DB: stop slave; set @@session.gtid_next='a42e8e2b-886a-11e7-962b-00155d1cca18:121'; begin; commit; set @@session.gtid_next=automatic; start slave; show slave statusG 感谢你能够认真阅读完这篇文章，希望小编分享的“mysql从库误删数据后和gtid复制断开后怎么处理”这篇文章对大家有帮助。 （编辑：晋中站长网） 【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容! |
