transaction_replay_max_size

Overview

Maximum size in bytes permitted for transaction replays.

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

DETAILS

In cases where an in-progress transaction fails to execute on the Primary Server, the router can attempt to replay the transaction. This can result in MariaDB MaxScale recovering from a failed Primary, hiding the transaction failure from the client.

This module parameter sets the maximum size in bytes for transactions the router replays.

CHANGE HISTORY

Release Series

History

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.1.

EXTERNAL REFERENCES