My replication stopped with error Last_SQL_Errno: 1032 or Last_SQL_Errno: 1062
example error:
Last_SQL_Error: Could not execute Delete_rows event on table cportal.b_search_content_stem; Can’t find record in ‘b_search_content_stem’, Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event’s master log mk-db1-master-bin.000488, end_log_pos 74862564
das-ich,
The error message you posted said that one row to be deleted from cportal.b_search_content_stem could not be found in the slave. This suggested that slave’s data is not consistent with the master. You can use STOP SLAVE; SET GLOBAL sql_slave_skip_counter = 1; START SLAVE to skip this statement and resume replication. Then use pt-table-checksum/pt-table-sync to check and fix the data discrepancy between master and slave.
For the use of pt-table-checksum/pt-table-sync, you can refer to the documentation at:
[URL]http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html[/URL]
[URL]http://www.percona.com/doc/percona-toolkit/2.2/pt-table-sync.html[/URL]