From 501ea809a839f4610e3442c3ada32741a28c0e0f Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Thu, 11 Jun 2015 17:02:07 +0300 Subject: [PATCH] Fixed typos in documentation. --- Documentation/Routers/SchemaRouter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/Routers/SchemaRouter.md b/Documentation/Routers/SchemaRouter.md index 951eed6b5..02d6f8e50 100644 --- a/Documentation/Routers/SchemaRouter.md +++ b/Documentation/Routers/SchemaRouter.md @@ -46,7 +46,7 @@ The schemarouter supports the following router options: |option |parameter |description| |-------------------|-----------|-----------| -|max_sescmd_hitory |integer |Set a limit on the number of session modifying commands a session can execute. This sets an effective cap on the memory consupmtion of the session.| +|max_sescmd_history |integer |Set a limit on the number of session modifying commands a session can execute. This sets an effective cap on the memory consumption of the session.| |disable_sescmd_history|true, false|Disable the session command history. This will prevent growing memory consumption of a long-running session and allows pooled connections to MaxScale to be used. The drawback of this is the fact that if a server goes down, the session state will not be consistent anymore.| |refresh_databases|true, false|Enable database map refreshing mid-session. These are triggered by a failure to change the database i.e. `USE ...``queries.| |refresh_interval|float|The minimum interval between database map refreshes in seconds.|