Replication and Binary Logging Options and Variables ddl_exist_errors Command-Line Format --slave-sql-verify-checksum[={OFF| ON}] System Variable slave_sql_verify_checksum Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Boolean Default Value ON Command-Line Format --slave-transaction-retries=# System Variable slave_transaction_retries Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 10 Minimum Value 0 Maximum Value (64-bit platforms) 18446744073709551615 Maximum Value (32-bit platforms) 4294967295 Normally, replication stops when an error occurs on the replica, which gives you the opportunity to resolve the inconsistency in the data manually. This variable causes the replication SQL thread to continue replication when a statement returns any of the errors listed in the variable value. Cause the replication SQL thread to verify data using the checksums read from the relay log. In the event of a mismatch, the replica stops with an error. Setting this variable takes effect for all replication channels immediately, including running channels. The replication I/O thread always reads checksums if possible when accepting events from over the network. Sets the maximum number of times for replication SQL threads on a single-threaded or multithreaded replica to automatically retry failed transactions before stopping. Setting this variable takes effect for all replication channels immediately, including running channels. The default value is 10. Setting the variable to 0 disables automatic retrying of transactions. If a replication SQL thread fails to execute a transaction because of an  InnoDB  deadlock or because the transaction’s execution time exceeded  InnoDB ’s  innodb_lock_wait_timeout  or  NDB ’s TransactionDeadlockDetectionTimeout  or  TransactionInactiveTimeout , it automatically 3537 • slave_transaction_retries • slave_sql_verify_checksum Note