From 3ae177f4e88d446f898c19c6bd92832049c7a8b4 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Thu, 11 Jun 2015 16:58:39 +0300 Subject: [PATCH] Added documentation about refresh_databases and refresh_interval options. --- Documentation/Routers/SchemaRouter.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/Routers/SchemaRouter.md b/Documentation/Routers/SchemaRouter.md index 02d6f8e50..34da8506c 100644 --- a/Documentation/Routers/SchemaRouter.md +++ b/Documentation/Routers/SchemaRouter.md @@ -45,11 +45,11 @@ This would in effect allow the user 'john' to only see the database 'shard' on t The schemarouter supports the following router options: |option |parameter |description| -|-------------------|-----------|-----------| -|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.| +--------------------------------------------- +|max_sescmd_hitory | |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.| +|disable_sescmd_history||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||The minimum interval between database map refreshes in seconds. ## Limitations The schemarouter router currently has some limitations due to the nature of the sharding implementation and the way the session variables are detected and routed. Here is a list of the current limitations.