MySQL 5.1 with Maria Reference Manual :: 16 Replication :: 16.3 Replication Notes and Tips :: 16.3.1 Replication Features and Issues :: 16.3.1.24 Replication Retries and Timeouts
Section Navigation [Toggle]
- 16.3.1 Replication Features and Issues
- 16.3.1.1 Replication and AUTO_INCREMENT
- 16.3.1.2 Replication and Character Sets
- 16.3.1.3 Replication of CREATE ... IF NOT EXISTS Statements
- 16.3.1.4 Replication of CREATE TABLE ... SELECT Statements
- 16.3.1.5 Replication with Differing Tables on Master and Slave
- 16.3.1.6 Replication and DIRECTORY Table Options
- 16.3.1.7 Replication of DROP ... IF EXISTS Statements
- 16.3.1.8 Replication of Invoked Features
- 16.3.1.9 Replication with Floating-Point Values
- 16.3.1.10 Replication and FLUSH
- 16.3.1.11 Replication and System Functions
- 16.3.1.12 Replication and LIMIT
- 16.3.1.13 Replication and LOAD DATA
- 16.3.1.14 Replication and the Slow Query Log
- 16.3.1.15 Replication During a Master Crash
- 16.3.1.16 Replication During a Master Shutdown
- 16.3.1.17 Replication with MEMORY Tables
- 16.3.1.18 Replication of the System mysql Database
- 16.3.1.19 Replication and the Query Optimizer
- 16.3.1.20 Replication and Reserved Words
- 16.3.1.21 Slave Errors during Replication
- 16.3.1.22 Replication during a Slave Shutdown
- 16.3.1.23 Replication and Temporary Tables
- 16.3.1.24 Replication Retries and Timeouts
- 16.3.1.25 Replication and Time Zones
- 16.3.1.26 Replication and Transactions
- 16.3.1.27 Replication and Triggers
- 16.3.1.28 Replication and TRUNCATE
- 16.3.1.29 Replication and Variables
- 16.3.1.30 Replication and Views
The global system variable
slave_transaction_retries
affects replication as follows: If the replication slave SQL
thread fails to execute a transaction because of an
InnoDB deadlock or because it exceeded the
InnoDB
innodb_lock_wait_timeout value,
or the NDBCLUSTER
TransactionDeadlockDetectionTimeout or
TransactionInactiveTimeout value, the
transaction is automatically retried
slave_transaction_retries times
before stopping with an error. The default value is 10. The
total retry count can be seen in the output of
SHOW STATUS; see
Section 5.1.7, “Server Status Variables”.
User Comments
Add your own comment.