Module Parameters for MariaDB MaxScale 2.4
This page is part of MariaDB's MariaDB Documentation.
The parent of this page is: Reference for MariaDB MaxScale 2.4
Topics on this page:
MariaDB MaxScale 2.4 supports many module parameters.
Reference material is available for MariaDB MaxScale 2.4.
MariaDB MaxScale 2.4 Module Parameters
The Module Parameters supported by MariaDB MaxScale 2.4 are listed below.
To see Module Parameters supported in other versions, see "Module Parameters by MariaDB MaxScale Version".
MariaDB Monitor (mariadbmon)
The parameters for mariadbmon:
Require that the Primary Server have connectivity with at least one running Replica Server
Requires that Replica Servers have connectivity with a running Primary Server
Requires that the Primary Server have at least one Replica Server
Number of consecutive times MaxScale can fail to reach the Primary Server before it considers it down
Read/Write Split Router (readwritesplit)
The parameters for readwritesplit:
Configures read causality, reads subsequent to writes issued in manner to reduce replication lag
Timeout for synchronization of the Primary Server with a Replica Server during causal reads
Retry queries that fail to route due to connection issues
Timeout for retrying queries that fail to route due to connection issues
Route read operations to the Primary Server or whether it only accepts write operations
Reconnect to the Primary Server if it changes mid-session
Maximum number of connections the router session can use to connect to Replica Servers
Number of seconds a Replica Server is allowed to fall behind the Primary Server
Criteria the router uses to select Replica Servers in load balancing read operations
Routes multi-statement queries to the Primary Server
Replays in progress transactions that fail on a different Server
Maximum number of times to attempt to replay failed transactions
Maximum size in bytes permitted for transaction replays
Maximum number of times the router attempts to replay transactions in the event that the transaction fails due to deadlocks
Where the router sends session variable queries