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

MXS-2314 Add 'cluster' parameter to service

Browse Source 
Using the cluster parameter, the servers of a service can be
defined using a monitor.

This change basically only introduces the parameter.
This commit is contained in:
Johan Wikman
2019-02-06 13:43:29 +02:00
parent 1073bc1832
commit f271c5cea1
6 changed files with 103 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
Documentation/Changelog.md
View File

@ -5,6 +5,7 @@
* Names starting with `@@` are reserved for use by MaxScale.
* Names can no longer contain whitespace.
* Servers can now be drained.
* The servers of a service can now be defined using a monitor.
For more details, please refer to:

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

@ -1030,6 +1030,20 @@ in the name section of a block with a type parameter of server (see below).
servers=server1,server2,server3
```
*NOTE* The `servers` parameter is mutually exclusive with the `cluster` parameter.
#### `cluster`
The servers the service uses are defined by the monitor specified as value
of this configuration parameter.
```
cluster=TheMonitor
```
*NOTE* The `clusters` parameter is mutually exclusive with the `servers` parameter.
#### `user`
The user parameter, along with the password parameter are used to define the

13
Documentation/Release-Notes/MaxScale-2.4.0-Release-Notes.md
View File

@ -63,6 +63,19 @@ being drained is the master, then it will not be possible to connect
unless `master_failure_mode` has been set to something else but the
default `fail_instantly`.
### Cluster
The servers a service uses can now be specified using the `cluster`
parameter of the service.
```
[TheService]
...
cluster=TheMonitor
```
In this case, the servers of the service will be defined by the
referred to monitor. Note that the parameters `servers` and `cluster`
are mutually exclusive.
## Bug fixes
[Here is a list of bugs fixed in MaxScale 2.4.0.](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.4.0)