Shulou(Shulou.com)05/31 Report--

This article mainly introduces how to deal with mysql after mistakenly deleting data from the database and after gtid replication is disconnected, it has a certain reference value, and interested friends can refer to it. I hope you can learn a lot after reading this article.

Situation: the data should be deleted on the main library, but it was deleted from the library first, and then the synchronization of the slave library was disconnected when the master database was deleted again.

Error report:

Root@xhh_test 01:58:58 > SHOW SLAVE status\ G

* * 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 muri 00155d1cca18pur121' 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 muri 00155d1cca18pur121' 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:

# # find the corresponding transaction number and skip the specified gtid

Stop slave

Set @ @ session.gtid_next='a42e8e2b-886a-11e7-962b Israel 00155d1cca18pur121'

Begin

Commit

Set @ @ session.gtid_next=automatic

Start slave

Show slave status\ G

Thank you for reading this article carefully. I hope the article "how to deal with mysql after mistakenly deleting data from the database and what to do after gtid replication is disconnected" shared by the editor is helpful to everyone. At the same time, I also hope that you can support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.