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

Fix max_sescmd_history documentation

Browse Source 
The session commands are now always stored but they are stored as
references. Also clarified that the feature was disabled in older
versions.
This commit is contained in:
Markus Mäkelä 2018-10-15 16:02:38 +03:00
parent 2f76c48b06
commit a2ef874fe6
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Documentation/Routers/ReadWriteSplit.md
View File

@ -215,17 +215,18 @@ the slave with the least amount of connections
**`max_sescmd_history`** sets a limit on how many distinct session commands each
session can execute before the session command history is disabled. The default
is 50 session commands.
is 50 session commands starting with MaxScale 2.3.0. In older versions, the
session command history was disabled by default.
```
# Set a limit on the session command history
max_sescmd_history=1500
```
The first and last execution of each session command is stored. This means that
with `N` distinct session commands, the minimum value of `max_sescmd_history` to
guarantee that all of them are kept in the history is `N * 2`. In practice, the
real history size required to store the commands is closer to `N`.
When a session command is executed for the first time, it is stored in
memory. Any subsequent executions of the same command are stored as references
to the original command. By storing references instead of copies of the data,
the amount of memory used is reduced.
If you have long-running sessions which change the session state often, increase
the value of this parameter if server reconnections fail due to disabled session