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

Updated documentation.

Browse Source
This commit is contained in:
Markus Makela
2015-04-23 21:05:50 +03:00
parent 675ecd7e2d
commit 2a35ed1c47
2 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Getting-Started/Configuration-Guide.md
View File

@ -823,6 +823,8 @@ In above-mentioned case the user-defined variable would only be updated in the m
When a limitation is set, it effectively creates a cap on the session's memory consumption. This might be useful if connection pooling is used and the sessions use large amounts of session commands.
`disable_sescmd_history=true|false` disables the session command history. This way nothing is stored and if a slave server fails and a new one is taken in its stead, the session on that server will be in an inconsistent state compared to the master server. Disabling session command history will allow connection pooling without causing a constant growth in the memory consumption.
An example of Read/Write Split router configuration :
```