–slave-skip-errors=[err_code1,err_code2, … | all | ddl_exist_errors]
Normally, replication stops when an error occurs on the replica, which gives you the opportunity to resolve the inconsistency in the data manually. This option causes the replication SQL thread to continue replication when a statement returns any of the errors listed in the option value.
Normally, replication is interrupted when there is an ERROR, giving the opportunity to resolve the data inconsistencies manually. Slave-skip-errors causes the SQL thread to ignore these errors and continue copying.
Do not use this option unless you fully understand why you are getting errors. If there are no bugs in your replication setup and client programs, and no bugs in MySQL itself, an error that stops replication should never occur. Indiscriminate use of this option results in replicas becoming hopelessly out of synchrony with the source, with you hawww.pizei.comving no idea why this has occurred.
Do not use this parameter freely unless you fully understand why the error is being reported. In the replication configuration, if the client has no errors, MySQL itself has no bugs, the replication will not be interrupted. Arbitrary use of this parameter can result in inconsistency between master and slave.
For error codes, you should use the numbers provided by the error message in the replica’s error log
and in the output of SHOW SLAVE STATUS. Appendix B, Error Messages and Common Problems, lists server error codes.
For incorrect codes, you can view the output page of Show Slave Status.
The shorthand value ddl_exist_errors is equivalent to the error code list
1007,1008,1050,1051,1054,1060,1061,1068,1094,1146.
Face reading lists is common ddl_exist_errors, 1007100, 8105, 0105, 1105, 4106, 0106, 1106, 8109, 4114 (6).
You can also (but should not) use the very nonrecommended value of all to cause the replica to ignore all error messages and keeps going regardless of what happens. Needless to say, if you use all, there are no guarantees regarding the integrity of your data. Please do not complain (or file bug reports) in this case if the replica’s data is not anywhere close to what it is on the source. You have been warned.
Examples:
– slave – skip – errors = 1062105 3
–slave-skip-errors=all
–slave-skip-errors=ddl_exist_errors