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_masterbin. 000003' position 684 Why did you receive this error?（）

Consider the following statement on a RANGE partitioned table: ALTER TABLE orders DROP PARTITION p1, p3;
What is the outcome of executing the above statement?（）

A simple master-to-slave replication is currently being used. The following information is extracted from the SHOW SLAVE STATUS output:
Last_SQL_Error: Error 'Duplicate entry '8' for key 'PRIMARY' ' on query.
Default database: 'mydb'. Query: 'insert into mytable VALUES ('8' , 'George') ' Skip_Counter: 0 Retrieved _Gtid_Set: 38f32e23480a7-32a1-c323f78067fd37821: 1-8 Auto _Position: 1
You execute a "SHOW CREATE TABLE mytable" on the slave: CREATE TABLE 'mytable' ( 'ID' int(11) NOT NULL
DEFAULT '0', 'name' char(10) DEFAULT NULL, PRIMARY KEY ('ID') )
The table mytable on the slave contains the following:

You have issued a STOP SLAVE command. One or more statements are required before you can issue a START SLAVE command to resolve the duplicate key error. Which statement should be used（）