1Z0-883 · Question #28
A MySQL replication slave is set up as follows: - User all InnoDB tables - Receives ROW-based binary logs - Has the read-only option The replication slave has been found in an error state. You check…
The correct answer is A. The slave was created with mysqldump u root p skip-lock-table--all-databases > /data/data.sql E. The applications have the SUPER privilege, which allows them to update rows. See the full explanation below for the reasoning.
Question
A MySQL replication slave is set up as follows:
- User all InnoDB tables
- Receives ROW-based binary logs
- Has the read-only option
The replication slave has been found in an error state. You check the MySQL error log file and find the following entries:
2013-08-27 13:55:44 9056 [ERROR] Slave SQL: Could not execute Write_rows event on table test.tl; Duplicate entry 3' for key'PRIMARY' , Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log 56_master-bin.000003, end_log_pas 653, Error_code: 1062 2013-08-27 13:55:44 9056 [Warning] Salve: Duplicate entry 3' for key PRIMARY' Error_code: 1062 2013-08-27 13:55:44 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 496 What are two possible causes for this error to occur?
Options
- AThe slave was created with mysqldump u root p skip-lock-table--all-databases > /data/data.sql
- BThe slave user does have INSERT, UPDATE, or DELETE permission and cannot execute the
- CFor tables with UNIQUE keys, statement-based replication must be used maintain integrity.
- DThe root user on the slave has executed FLUSH LOGS, causing the relay-log to doublewrite.
- EThe applications have the SUPER privilege, which allows them to update rows.
How the community answered
(49 responses)- A82% (40)
- B10% (5)
- C6% (3)
- D2% (1)
Community Discussion
No community discussion yet for this question.