slave_ replication_ lag
This page is part of MariaDB's MariaDB Documentation.
The parent of this page is: Module Parameters for MariaDB MaxScale
Topics on this page:
Number of seconds a Replica Server is allowed to fall behind the Primary Server.
See also: Module Parameters for MariaDB MaxScale 23.02, in 22.08, in 6, in 2.5, and in 2.4
See also: Module Parameters for MariaDB MaxScale 23.02, in 22.08, and in 6
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.