From 4f964ad039f57f5a3a5cc28c63d9542aa425cf65 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Wed, 29 Apr 2020 17:49:21 +0300 Subject: [PATCH] Clarify CCRFilter documentation The example now states that the effects of the filter are only seen by individual sessions. --- Documentation/Filters/CCRFilter.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/Filters/CCRFilter.md b/Documentation/Filters/CCRFilter.md index 663cdcd45..26ce97df5 100644 --- a/Documentation/Filters/CCRFilter.md +++ b/Documentation/Filters/CCRFilter.md @@ -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.