mysql repaire_Repair MySQL Replication遇到的错误（一）
My SQL 复制过程中,sql post thread如果执行某个SQL出错，则会自动停止并且在日志和show slave status中提示错误信息。
090303 22:36:31 [ERROR] Slave SQL: Could not execute
Delete_rows event on table CATY.buyer_info; Can’t find record in
‘buyer_info’, Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the
event’s master log mysql-bin.000004, end_log_pos 1581, Error_code: 1032
090303 22:36:31 [Warning] Slave: Can’t find record in ‘buyer_info’ Error_code: 1032
090303 22:36:31 [ERROR] Error running query, slave SQL thread aborted.
Fix the problem, and restart the slave SQL thread with “SLAVE START”.
We stopped at log ‘mysql-bin.000004′ position 1425
mysql> SHOW SLAVE STATUS \G
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: qadb27.qa.ebay.com
Master_User: slave_user
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000004
Read_Master_Log_Pos: 1608
Relay_Log_File: qadb17-relay-bin.006018
Relay_Log_Pos: 251
Relay_Master_Log_File: mysql-bin.000004
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
CATY.buyer_info; Can’t find record in ‘buyer_info’, Error_code: 1032;
handler error HA_ERR_KEY_NOT_FOUND; the event’s master log
mysql-bin.000004, end_log_pos 1581
Skip_Counter: 0
Exec_Master_Log_Pos: 1425
Relay_Log_Space: 10066
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
CATY.buyer_info; Can’t find record in ‘buyer_info’, Error_code: 1032;
handler error HA_ERR_KEY_NOT_FOUND; the event’s master log
mysql-bin.000004, end_log_pos 1581
1 row in set (0.00 sec)
如果错误记录可以fix或者忽略,则可以设置GLOBAL SQL_SLAVE_SKIP_COUNTER忽略sql thread的错误。
mysql> STOP SLAVE;
Query OK, 0 rows affected (0.00 sec)
mysql> SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;
Query OK, 0 rows affected (0.00 sec)
mysql>START SLAVE;
Query OK, 0 rows affected (0.01 sec)
mysql> SHOW SLAVE STATUS \G
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: qadb27.qa.ebay.com
Master_User: slave_user
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000004
Read_Master_Log_Pos: 1608
Relay_Log_File: qadb17-relay-bin.006075
Relay_Log_Pos: 251
Relay_Master_Log_File: mysql-bin.000004
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: 1608
Relay_Log_Space: 552
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:
1 row in set (0.00 sec)
避免数据不一致可以在slave DB上设置GLOBAL read_only=true或者一定的用户权限。
也可编写高效的自动检测脚本重起sql thread。
是复制就会有数据不一致的问题的。