hcq/MaxScale
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 fbfbc9fda7
commit 7cdf32773f
2 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Documentation/Changelog.md
View File

@ -6,8 +6,11 @@ These are the changes introduced in the next MaxScale version. This is not the o
* Schemarouter now also allows for an upper limit to session commans.
* Schemarouter correctly handles SHOW DATABASES responses that span multiple buffers.
* Schemarouter now allows disabling of the session command history.
* Readwritesplit now allows disabling of the session command history.
* Logfiles have been renamed. The log names are now named error.log, messages.log, trace.log and debug.log.
## MaxScale 1.1
**NOTE:** MaxScale default installation directory has changed to `/usr/local/mariadb-maxscale` and the default password for MaxAdmin is now ´mariadb´.

2
Documentation/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 :
```