MySQL Skip Duplicate Replication Errors : skip replication error
Normally 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 and why they are failing, etc.
For example you can skip just one query that is hanging the slave using:
| mysql>SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE; |
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;):
| “1062 | Error ‘Duplicate entry ‘xyz’ for key 1′ on query. Default database: ‘db’. Query: ‘INSERT INTO …” |
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:
| slave-skip-errors = 1062 |
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:
| slave-skip-errors=[err_code1,err_code2,…|all] |
Posts to Review:
How to convert all tables from MyISAM into InnoDB? 
MYSQL Partitioning : What is and HOW To ? ERROR 1201 (HY000): Could not initialize master info structure; more error messages can be found in the MySQL error log Resolved : mysql replica : Relay log read failure: Could not parse relay log event entry.
[mysqld]
slave-skip-errors=1062,1053
[mysqld]
slave-skip-errors=1062
All other error numbers will stop the SQL thread and would require
STOP SLAVE;
SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1;
START SLAVE;
to have replication conitnue