View Single Post
  #6  
Old 31st August 2010, 23:08
Mark_NL Mark_NL is offline
Senior Member
 
Join Date: Sep 2008
Location: The Netherlands
Posts: 912
Thanks: 12
Thanked 99 Times in 95 Posts
Default

skipping slave errors should only be used if you know the problem that occured won't be of any problem for the rest of the replication .. the error tells you that there is already a record in that table with the same key ..

1. Do you have "read only" in your slave config?
2. Remember that a SUPER user is exempt for "read only" (they can always edit data on a read only server)
3. if you're sure you can continue do:

SLAVE_SKIP_ERRORS=1;
START SLAVE;
SHOW SLAVE STATUS;

and check if the "Seconds Behind master" field is decreasing..

good luck.
Reply With Quote