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

Merge branch '2.1' into develop

Browse Source
This commit is contained in:
Johan Wikman
2017-04-27 09:11:02 +03:00
parent de8febf9a9 656cb3c517
commit deb11ae6eb
51 changed files with 2233 additions and 3313 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
Documentation/Monitors/MM-Monitor.md
View File

@ -2,11 +2,15 @@
## Overview
The Multi-Master Monitor is a monitoring module for MaxScale that monitors Master-Master replication. It assigns master and slave roles inside MaxScale based on whether the read_only parameter on a server is set to off or on.
The Multi-Master Monitor is a monitoring module for MaxScale that monitors Master-Master replication.
It assigns master and slave roles inside MaxScale based on whether the read_only parameter on a server
is set to off or on.
## Configuration
A minimal configuration for a monitor requires a set of servers for monitoring and a username and a password to connect to these servers. The user requires the REPLICATION CLIENT privilege to successfully monitor the state of the servers.
A minimal configuration for a monitor requires a set of servers for monitoring and an username
and a password to connect to these servers. The user requires the REPLICATION CLIENT privilege
to successfully monitor the state of the servers.
```
[Multi-Master Monitor]
@ -20,7 +24,8 @@ passwd=mypwd
## Common Monitor Parameters
For a list of optional parameters that all monitors support, read the [Monitor Common](Monitor-Common.md) document.
For a list of optional parameters that all monitors support, read
the [Monitor Common](Monitor-Common.md) document.
## Multi-Master Monitor optional parameters
@ -28,9 +33,12 @@ These are optional parameters specific to the Multi-Master Monitor.
### `detect_stale_master`
Allow previous master to be available even in case of stopped or misconfigured replication. This allows services that depend on master and slave roles to continue functioning as long as the master server is available.
Allow previous master to be available even in case of stopped or misconfigured replication.
This allows services that depend on master and slave roles to continue functioning as long as
the master server is available.
This is a situation which can happen if all slave servers are unreachable or the replication breaks for some reason.
This is a situation which can happen if all slave servers are unreachable or the
replication breaks for some reason.
```
detect_stale_master=true