MySQL Replication :: Skip Duplicate Errors on Slave

MySQL_Ying-Yang_outline5_192x192Normally MySQL replication will stop whenever there is an error running a query on the slave. This happens in order for us to be able to identify the problem and fix it, and keep the data consistent with the mater that has sent the query. You can skip such errors, even if this is not recommended, as long as you know really well what are those queries, why they are failing, and how can they affect the replication work, etc.

For example you can skip just one query that is hanging the slave using:

There might be cases where you will want to skip more queries. For example you might want toskip all duplicate errors you might be getting (output from show slave status;):

If you are sure that skipping those errors will not bring your slave inconsistent and you want to skip them ALL, you would add to your my.cnf:

As shown above in my example 1062 is the error you would want to skip, and from here we have: _ Error: 1062 SQLSTATE: 23000 (ER_DUP_ENTRY) Message: Duplicate entry ‘%s’ for key %d_

You can skip also other type of errors, but again don’t do this unless you understand very well what those queries are and what impact they have on your data:

and for the error codes you can see them all here … (you will see them in your

also).

Leave a Reply