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

How to understand Mysql GITD replication interrupt handling, I believe that many inexperienced people do not know what to do, so this paper summarizes the causes of the problem and solutions, through this article I hope you can solve this problem.

Replication errors were found from the library:

"root@localhost:mysqld.sock [test] > show slave status\ G

* * 1. Row *

Slave_IO_State: Waiting for master to send event

Master_Host: 192.168.2.54

Master_User: repl

Master_Port: 3306

Connect_Retry: 60

Master_Log_File: mysql-bin.000010

Read_Master_Log_Pos: 2513

Relay_Log_File: virtdb55-relay-bin.000002

Relay_Log_Pos: 1305

Relay_Master_Log_File: mysql-bin.000010

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: 1051

Last_Error: Error 'Unknown table' test.t1'' on query. Default database: 'test'. Query: 'DROP TABLE "T1" / * generated by server * /'

Skip_Counter: 0

Exec_Master_Log_Pos: 1135

Relay_Master_Log_File: mysql-bin.000010: read the master log file location for the sql thread from the library

Exec_Master_Log_Pos: 1135: read from the library sql thread to the master log pos location

Solution: retrieve the operation content according to the read position of the SQL thread

Mysqlbinlog-vvv mysql-bin.000010-- start-position=1135

# at 1135

# 160519 9:24:50 server id 54 end_log_pos 1183 CRC32 0x5edc0e52 GTID [commit=yes]

SET @ @ SESSION.GTID_NEXT= '8b8cad8e-053c-11e6-b500-5254006f0b84pur6 "Universe" /

# at 1183

# 160519 9:24:50 server id 54 end_log_pos 1298 CRC32 0x3c2cbffc Query thread_id=3 exec_time=0 error_code=0

Use `test` / *! * /

SET timestamp 1463621090

DROP TABLE "T1" / * generated by server * /

/ *! * /

SET @ @ SESSION.GTID_NEXT= '8b8cad8e-053c-11e6-b500-5254006f0b84pur6 monthly event; set this event to skip the event.

Skip the replication error

Stop slave

SET @ @ SESSION.GTID_NEXT= '8b8cad8e-053c-11e6-b500-5254006f0b84pur6 "Universe" /

Begin;commit

Set gtid_next= "AUTOMATIC"

Start slave

After reading the above, have you mastered how to understand the handling of Mysql GITD replication interrupts? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

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.