max_slave_replication_lag

Overview

Number of seconds a Replica Server is allowed to fall behind the Primary Server.

See also: Module Parameters for MariaDB MaxScale 22.08 and in 6

DETAILS

In asynchronous and semi-synchronous replication, Replica Servers can fall behind the Primary Server, due to limitations of hardware or workload. This is called replication lag. Lagging Replica Servers do not provide current data to clients executing read queries.

This module parameter controls the amount of replication lag the router permits. If a Replica Server falls too far behind, the router stops routing client connections to it. This is to allow the Replica Server to catch up with the Primary Server and to prevent it from serving old data to clients.

CHANGE HISTORY

Release Series

History

22.08

  • Present starting in MariaDB MaxScale 22.08.0.

6

  • Present starting in MariaDB MaxScale 6.0.0.

EXTERNAL REFERENCES