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

MXS-1080: Document max_slave_replication_lag behavior

Browse Source 
The max_slave_replication_lag parameter for readwritesplit only works for
monitors that detect replication lag. As the MySQL monitor is the only one
that implements this functionality, the parameter only has meaning when
used with master-slave clusters.
This commit is contained in:
Markus Mäkelä 2017-01-19 13:10:46 +02:00
parent fed61fde98
commit 98c2d37156
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Documentation/Routers/ReadWriteSplit.md
View File

@ -32,6 +32,9 @@ This feature is disabled by default.
This applies to Master/Slave replication with MySQL monitor and `detect_replication_lag=1` options set.
Please note max_slave_replication_lag must be greater than monitor interval.
This option only affects Master-Slave cluster. Galera clusters do not have a
concept of slave lag even if the application of write sets might have lag.
### `use_sql_variables_in`