transaction_replay_retry_on_deadlock
This page is part of MariaDB's Enterprise Documentation.
The parent of this page is: Module Parameters for MariaDB MaxScale
Topics on this page:
Overview
- In 6, 2.5, 2.4:
Maximum number of times the router attempts to replay transactions in the event that the transaction fails due to deadlocks.
- In 2.3:
Not present
See also: Module Parameters for MariaDB MaxScale 6, in 2.5, in 2.4, and in 2.3
DETAILS
In cases where an in-progress transaction fails to execute on the Primary Server, the router can re-route the query to a Replica Server promoted to serve as the new Primary. This can result in MariaDB MaxScale recovering from a failed Primary, hiding the transaction failure from the client.
This module parameter controls the maximum number of times the router attempts to replay transactions in the event that the transaction fails due to deadlocks.
EXTERNAL REFERENCES
Information specific to MariaDB SkySQL can be found on the transaction_replay_retry_on_deadlock page in the SkySQL Documentation.