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

MXS-1780 Make retain_last_statements service specific

Browse Source
This commit is contained in:
Johan Wikman
2018-11-07 11:44:25 +02:00
parent 2bd2b4a32e
commit 32f2e769f4
9 changed files with 62 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
Documentation/Getting-Started/Configuration-Guide.md
View File

@ -1230,6 +1230,22 @@ The following Server side config is needed too.
session_track_transaction_info = CHARACTERISTICS
```
#### `retain_last_statements`
How many statements MaxScale should store for each session of this service.
This overrides the value of the global setting with the same name. If
`retain_last_statements` has been specified in the global section of the
MaxScale configuration file, then if it has _not_ been explicitly specified
for the service, the global value holds, otherwise the service specific
value rules. That is, it is possible to enable the setting globally and
turn it off for a specific service, or just enable it for specific services.
The value of this parameter can be changed at runtime using `maxctrl` and the
new value will take effect for sessions created thereafter.
```
maxctrl alter service MyService retain_last_statements 5
```
### Server
Server sections are used to define the backend database servers that can be

5
Documentation/Release-Notes/MaxScale-2.3.1-Release-Notes.md
View File

@ -51,6 +51,11 @@ feature can be used for debugging, if there is suspicion that MaxScale
sends a particular statement to the wrong server (e.g. to a slave when it
should be sent to the master).
### Services
The global configuration parameter `retain_last_statements` can now
also be specified separately for individual services.
## Bug fixes
[Here is a list of bugs fixed in MaxScale 2.3.1.](https://jira.mariadb.org/issues/?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%202.3.1)