transaction_replay_retry_on_deadlock

Overview

Maximum number of times the router attempts to replay transactions in the event that the transaction fails due to deadlocks.

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.

CHANGE HISTORY

Release Series

History

22.08

  • Present starting in MariaDB MaxScale 22.08.1.

6

  • Present starting in MariaDB MaxScale 6.0.0.

2.5

  • Present starting in MariaDB MaxScale 2.5.0.

2.4

  • Added in MariaDB MaxScale 2.4.6.

Release Series

History

22.08

  • Present starting in MariaDB MaxScale 22.08.1.

6

  • Present starting in MariaDB MaxScale 6.0.0.