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

Remove documentation for monitor parameter

Browse Source 
The use of monitors in services isn't complete but this was not in the
documentation. A more complete solution should be done at a later date and
the current documentation should be removed.
This commit is contained in:
Markus Mäkelä 2017-02-08 08:34:34 +02:00
parent b0cf8c6e38
commit 4f7b2b545e
2 changed files with 0 additions and 45 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -589,42 +589,6 @@ filters=counter | QLA
The requests pass through the filters from left to right in the order defined in
the configuration parameter.
#### `monitor`
The monitor parameter tells the service which cluster of servers to use. The
value of the option is the name of a monitor object. This removes the redundant
definition of servers in both services and monitors.
If both the `monitor` and `servers` parameters are defined, only the `monitor`
parameter will be used.
Only one cluster can be defined for a service. Multi-cluster setups should use
the `servers` parameter to list the servers that the service should use.
Here is an excerpt from an example configuration with a service that defines the
cluster parameter.
```
[db-cluster-1-monitor]
type=monitor
module=mysqlmon
servers=server1,server2,server3
user=maxuser
passwd=maxpwd
monitor_interval=1000
[my-readwrite-service]
type=service
router=readwritesplit
monitor=db-cluster-1-monitor
user=maxuser
passwd=maxpwd
```
The _db-cluster-1-monitor_ cluster consists of three servers monitored by a
_mysqlmon_ monitor module. The _my-readwrite-service_ uses this monitor as the
source for servers.
#### `servers`
The servers parameter in a service definition provides a comma separated list of

9
Documentation/Release-Notes/MaxScale-2.1.0-Release-Notes.md
View File

@ -188,15 +188,6 @@ allowing runtime tuning of parameters.
- `destroy monitor`: Destroy a created monitor
- `alter monitor`: Alter monitor parameters
### Monitors as server sources for services
Services now accept a `monitor` parameter which can be used to point a service
to a cluster of servers that are monitored by a monitor. The value of the
`monitor` parameter should be the name of a monitor in the configuration name.
For more details, refer to the [Configuration
Guide](../Getting-Started/Configuration-Guide.md#cluster) section on clusters.
### Module commands
Introduced in MaxScale 2.1, the module commands are special, module-specific