content_image/840028.jpg content_image/840029.jpg content_image/840040.jpg content_image/840030.jpg
<img src='content_image/840028.jpg'>

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. 

• slave_sql_verify_checksum 

<img src='content_image/840029.jpg'>

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. 

<img src='content_image/840040.jpg'>

• slave_transaction_retries 

## Note 

The replication I/O thread always reads checksums if possible when accepting events from over the network. 

<img src='content_image/840030.jpg'>

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 

