| MySQL Replication: Is it possible to ignore possible errors on slave? [message #1966] |
Sat, 29 September 2007 13:25  |
esudnik Messages: 9 Registered: March 2007 |
Junior Member |
|
|
I have replication from master server to slave. The slave server data is not 100% "clean" and sometimes I get a replication error like duplicate key (see following log entry):
070928 20:28:08 [ERROR] Slave: Error 'Duplicate entry '478519012' for key 1' on query. Default database: 'community'. Query: 'INSERT INTO user_access (ID,SESSION_ID,IP,AID,ANONYMOUS_FLAG,NEW_VISIT_FLAG,DATE_CRE ATED) VALUES (478519012,'55567510deb4776a3acbc057990bf83e','89.178.91.165 ','akter',1,0,1191000486)', Error_code: 1062
070928 20:28:08 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000001' position 685190145
0
... the big problem is that after this error the replication stops to work and I must start it manually after deleting bad entry.
Is it posible to ignore errors like this? (with any config option or something like that)
|
|
|