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

Clarify CCRFilter documentation

Browse Source 
The example now states that the effects of the filter are only seen by
individual sessions.
This commit is contained in:
Markus Mäkelä 2020-04-29 17:49:21 +03:00
parent 910cee3538
commit 4f964ad039
No known key found for this signature in database
GPG Key ID: 5CE746D557ACC499
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/Filters/CCRFilter.md
View File

@ -106,11 +106,11 @@ module=ccrfilter
time=5
```
This configuration will force all read queries after a write to the master for 5
seconds, preventing read scaling until the modifications have been replicated to
the slaves.
With this configuration, whenever a connection does a write, all subsequent
reads done by that connection will be forced to the master for 5 seconds.
For best performance, the value of _time_ should be slightly greater than the
actual replication lag between the master and its slaves. If the number of
critical read statements is known, the _count_ parameter could be used to
This prevents read scaling until the modifications have been replicated to the
slaves. For best performance, the value of _time_ should be slightly greater
than the actual replication lag between the master and its slaves. If the number
of critical read statements is known, the _count_ parameter could be used to
control the number reads that are sent to the master.