Replication Issue - Slave (Duplicate Entry)
We are running master slave replication on mysql 5.7 it was running fine from last 1 year but now we are facing issue and found some serious data syncing issue. I found some serious data difference in one of our main table and mysqld.log is showing following errors repetitively:
2019-10-18T14:31:46.343746Z 606179825 [Note] Slave SQL for channel '': Could not execute Update_rows event on table so.sns_cods_logs; Duplicate
entry '7108207-4129' for key 'index_unique', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log master_bin.000581, end_log_pos 5593918
83, Error_code: 1062
2019-10-18T14:31:46.871730Z 606179825 [Note] Slave SQL for channel '': Could not execute Update_rows event on table so.sns_cods_logs; Duplicate
entry '7108207-4126' for key 'index_unique', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log master_bin.000581, end_log_pos 5596572
30, Error_code: 1062
My replication settings are as follow:
server-id = 236
slave-skip-errors = 1062,1032,1146,1539,1022
innodb_flush_log_at_trx_commit = 2
I have performed a test on master server and manually update a row then find the row on slave side but once I again update the same row I didn't find and see above errors in mysqld.log file. What
Subject
Views
Written By
Posted
Replication Issue - Slave (Duplicate Entry)
4021
October 19, 2019 05:33AM
1159
October 19, 2019 10:06AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.