Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Not a Bug
-
Affects Version/s: 10.0.7
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Ubuntu 12.04 LTS
Description
mysql> show slave status \G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.0.40
Master_User: slave_user
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000221
Read_Master_Log_Pos: 242775
Relay_Log_File: mysql-relay.000010
Relay_Log_Pos: 168849715
Relay_Master_Log_File: mysql-bin.000204
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 Update_rows_v1 event on table bacula.Media; Can't find record in 'Media', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log mysql-bin.000204, end_log_pos 168850009
Skip_Counter: 0
Exec_Master_Log_Pos: 385542863
Relay_Log_Space: 288242036
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 Update_rows_v1 event on table bacula.Media; Can't find record in 'Media', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log mysql-bin.000204, end_log_pos 168850009
Replicate_Ignore_Server_Ids:
Master_Server_Id: 2
Master_SSL_Crl:
Master_SSL_Crlpath:
Using_Gtid: No
Gtid_IO_Pos:
1 row in set (0.01 sec)
ERROR:
No query specified
mysql>
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
This usually happens when master and slave tables go out of sync. There can be many reasons for this to happen. For example, you might have used statement-based replication and executed an "unsafe" (for statement-based) command. Or you might have manually edited tables on the slave. Of course, this could also happen as a result of a bug.
If it is, indeed, a bug and you have a test case that shows how to repeat this error, please, don't hesitate to reopen this bug report.