From 3145ebac433a4e9621c39ef359e4bd80711275d6 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Fri, 20 Feb 2015 16:39:41 +0200 Subject: [PATCH] Added documentation about the way that readwritesplit stores session commands. --- Documentation/Getting-Started/Configuration-Guide.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/Getting-Started/Configuration-Guide.md b/Documentation/Getting-Started/Configuration-Guide.md index 6c6d0b16c..893c937d8 100644 --- a/Documentation/Getting-Started/Configuration-Guide.md +++ b/Documentation/Getting-Started/Configuration-Guide.md @@ -710,6 +710,8 @@ Session commands include for example: **NOTE: if variable assignment is embedded in a write statement it is routed to _Master_ only. For example, `INSERT INTO t1 values(@myvar:=5, 7)` would be routed to _Master_ only.** +The router stores all of the executed session commands so that in case of a slave failure, a replacement slave can be chosen and the session command history can be repeated on that new slave. This means that the router stores each executed session command for the duration of the session. Applications that use long-running sessions might cause MaxScale to consume a growing amount of memory unless the sessions are closed. This can be solved by setting a connection timeout on the application side. + #### Configuring the Read/Write Split router Read/Write Split router-specific settings are specified in the configuration file of MaxScale in its specific section. The section can be freely named but the name is used later as a reference from listener section.