hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

MXS-2329 Use durations in readwritesplit

Browse Source
This commit is contained in:
Johan Wikman
2019-04-29 13:38:32 +03:00
parent ca51316364
commit ea243fd8ba
3 changed files with 55 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
Documentation/Routers/ReadWriteSplit.md
View File

@ -89,7 +89,14 @@ can't be used for routing.
This feature is disabled by default.
max_slave_replication_lag=<allowed lag in seconds>
max_slave_replication_lag=<allowed lag>
The lag is specified as documented
[here](../Getting-Started/Configuration-Guide.md#durations). If no explicit unit
is provided, the value is interpreted as seconds in MaxScale 2.4. In subsequent
versions a value without a unit may be rejected. Note that since the granularity
of the lag is seconds, a lag specified in milliseconds will be rejected, even if
the duration is longer than a second.
The Readwritesplit-router does not detect the replication lag itself. A monitor
such as the MariaDB-monitor for a Master/Slave-cluster is required. This option
@ -136,6 +143,13 @@ Send keepalive pings to backend servers. This feature was introduced in MaxScale
2.2.0. The default value is 300 seconds starting with 2.3.2 and for older
versions the feature was disabled by default.
The keepalive is specified as documented
[here](../Getting-Started/Configuration-Guide.md#durations). If no explicit unit
is provided, the value is interpreted as seconds in MaxScale 2.4. In subsequent
versions a value without a unit may be rejected. Note that since the granularity
of the keepalive is seconds, a keepalive specified in milliseconds will be rejected,
even if the duration is longer than a second.
The parameter value is the interval in seconds between each keepalive ping. A
keepalive ping will be sent to a backend server if the connection is idle and it
has not been used within `n` seconds where `n` is greater than or equal to the
@ -440,9 +454,16 @@ execution is an acceptable risk.
### `delayed_retry_timeout`
The number of seconds to wait until an error is returned to the client when
The duration to wait until an error is returned to the client when
`delayed_retry` is enabled. The default value is 10 seconds.
The timeout is specified as documented
[here](../Getting-Started/Configuration-Guide.md#durations). If no explicit unit
is provided, the value is interpreted as seconds in MaxScale 2.4. In subsequent
versions a value without a unit may be rejected. Note that since the granularity
of the timeout is seconds, a timeout specified in milliseconds will be rejected,
even if the duration is longer than a second.
### `transaction_replay`
Replay interrupted transactions. This parameter was added in MaxScale 2.3.0 and
@ -550,6 +571,13 @@ when the slave timed out.
The timeout for the slave synchronization done by `causal_reads`. The
default value is 10 seconds.
The timeout is specified as documented
[here](../Getting-Started/Configuration-Guide.md#durations). If no explicit unit
is provided, the value is interpreted as seconds in MaxScale 2.4. In subsequent
versions a value without a unit may be rejected. Note that since the granularity
of the timeout is seconds, a timeout specified in milliseconds will be rejected,
even if the duration is longer than a second.
### `lazy_connect`
Lazy connection creation causes connections to backend servers to be opened only