Replication and Binary Logging Options and Variables 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. 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 having no idea why this has occurred. For error codes, you should use the numbers provided by the error message in your replica’s error log and in the output of  SHOW REPLICA | SLAVE STATUS . Appendix B,  Error Messages and Common Problems , lists server error codes. The shorthand value  ddl_exist_errors  is equivalent to the error code list 1007,1008,1050,1051,1054,1060,1061,1068,1094,1146 . 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=1062,1053 --slave-skip-errors=all --slave-skip-errors=ddl_exist_errors • --slave-sql-verify-checksum={0|1} Command-Line Format --slave-sql-verify-checksum[={OFF| ON}] Type Boolean Default Value ON When this option is enabled, the replica examines checksums read from the relay log. In the event of a mismatch, the replica stops with an error. The following options are used internally by the MySQL test suite for replication testing and debugging. They are not intended for use in a production setting. • --abort-slave-event-count Command-Line Format --abort-slave-event-count=# Type Integer Default Value 0 Minimum Value 0 When this option is set to some positive integer  value  other than 0 (the default) it affects replication behavior as follows: After the replication SQL thread has started,  value  log events are permitted to 3516