1Z0-883 · Question #57
ROW-based replication has stopped working. You investigate the error log file and find the following entries: 2013-08-27 14:15:47 9056 [ERROR] Slave SQL: Could not execute Delete_rows event on table…
The correct answer is D. The slave SQL thread attempted to remove a row from the test.t1 table, but the row did not exist. See the full explanation below for the reasoning.
Question
ROW-based replication has stopped working. You investigate the error log file and find the following entries:
2013-08-27 14:15:47 9056 [ERROR] Slave SQL: Could not execute Delete_rows event on table test.t1; Can't find record in t1', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log 56_master-bin. 000003, end_log_pos 851, Error_code: 1032 2013-08-27 14:15:47 9056 [warning] Slave: Can't find record in t1' Error_code: 1032 2013-08-27 14:15:47 9056 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log `56_master- bin. 000003' position 684 Why did you receive this error?
Options
- AThe slave SQL thread does not have DELETE privileges to execute on test.t1 table.s
- BThe table definition on the slave -litters from the master.
- CMulti-threaded replication slaves can have temporary errors occurring for cross database updates.
- DThe slave SQL thread attempted to remove a row from the test.t1 table, but the row did not exist.
How the community answered
(36 responses)- A3% (1)
- B3% (1)
- C11% (4)
- D83% (30)
Community Discussion
No community discussion yet for this question.