From e2e220de661c45b65d37796f356097bdbfaf45e4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Mon, 2 Mar 2020 10:47:58 +0200 Subject: [PATCH] MXS-2726: Document ccrfilter default behavior Added an explicit mention of the way the filter works. --- Documentation/Filters/CCRFilter.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Documentation/Filters/CCRFilter.md b/Documentation/Filters/CCRFilter.md index a8ba14152..adde049bf 100644 --- a/Documentation/Filters/CCRFilter.md +++ b/Documentation/Filters/CCRFilter.md @@ -8,9 +8,10 @@ The Consistent Critical Read (CCR) filter allows consistent critical reads to be done through MaxScale while still allowing scaleout of non-critical reads. When the filter detects a statement that would modify the database, it attaches -a routing hint to all following statements. This routing hint guides the routing -module to route the statement to the master server where data is guaranteed to -be in an up-to-date state. +a routing hint to all following statements done by that connection. This routing +hint guides the routing module to route the statement to the master server where +data is guaranteed to be in an up-to-date state. Writes from one session do not, +by default, propagate to other sessions. ### Controlling the Filter with SQL Comments