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

MXS-1661 Introduce 'users_refresh_time'

Browse Source 
It is now possible to explicitly specify how frequently MaxScale
may refresh the users of a service.
This commit is contained in:
Johan Wikman
2018-02-09 11:40:17 +02:00
parent ae160f3ff2
commit b4760c5bbe
6 changed files with 80 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -548,6 +548,22 @@ has multiple interfaces.
local_address=192.168.1.254
```
#### `users_refresh_time`
How often, in seconds, MaxScale at most may refresh the users from the
backend server.
MaxScale will at startup load the users from the backend server, but if
the authentication of a user fails, MaxScale assumes it is because a new
user has been created and will thus refresh the users. By default, MaxScale
will do that at most once per 30 seconds and with this configuration option
that can be changed. The minimum allowed value is 10 seconds. A negative
value disables the refreshing entirelly. Note that using `maxadmin` it is
possible to explicitly cause the users of a service to be reloaded.
```
users_refresh_time=120
```
### Service
A service represents the database service that MariaDB MaxScale offers to the

6
Documentation/Release-Notes/MaxScale-2.1.14-Release-Notes.md
View File

@ -28,6 +28,12 @@ For any problems you encounter, please consider submitting a bug report at
## New Features
### Users Refresh Time
It is now possible to adjust how frequently MaxScale may refresh
the users of service. Please refer to the documentation for
[details](../Getting-Started/Configuration-Guide.md#users_refresh_time).
### Local Address
It is now possible to specify what local address MaxScale should