In 6, 2.5, 2.4:

Maximum number of times to attempt to replay failed transactions.

In 2.3:

Not present

See also: Module Parameters for MariaDB MaxScale 6, in 2.5, in 2.4, and in 2.3


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 number of times the router attempts to replay transactions.