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

minor docs fixes

Browse Source
This commit is contained in:
Timofey Turenko
2017-04-21 23:29:10 +03:00
committed by Markus Mäkelä
parent b85b4010f2
commit 047ac55a40
10 changed files with 28 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/Monitors/MySQL-Monitor.md
View File

@ -35,9 +35,9 @@ These are optional parameters specific to the MySQL Monitor.
### `detect_replication_lag`
A truth value which controls if replication lag between the master and the
A boolean value which controls if replication lag between the master and the
slaves is monitored. This allows the routers to route read queries to only
slaves that are up to date. Default value for this parameter is false.
slaves that are up to date. Default value for this parameter is _false_.
To detect the replication lag, MaxScale uses the _maxscale_schema.replication_heartbeat_
table. This table is created on the master server and it is updated at every heartbeat