hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added documentation about refresh_databases and refresh_interval options.

Browse Source
This commit is contained in:
Markus Makela
2015-06-11 16:58:39 +03:00
parent 94eb1b4eb1
commit 3ae177f4e8
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Documentation/Routers/SchemaRouter.md
View File

@ -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: The schemarouter supports the following router options:
|option |parameter |description| |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.| |max_sescmd_hitory |<int> |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|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.| |disable_sescmd_history|<boolean>|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_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.| |refresh_interval|<float>|The minimum interval between database map refreshes in seconds.
## Limitations ## 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. 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.