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

MXS-2441: Document galeramon changes

Browse Source 
Added a section that describes how galeramon behaves when it is configured
to monitor non-Galera servers that are replicating from Galera nodes.
This commit is contained in:
Markus Mäkelä 2019-04-17 15:57:22 +03:00
parent 60c1b15d60
commit 111ab8f5e4
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Documentation/Monitors/Galera-Monitor.md
View File

@ -1,5 +1,7 @@
# Galera Monitor
[[TOC]]
## Overview
The Galera Monitor is a monitoring module for MaxScale that monitors a Galera
@ -12,6 +14,14 @@ By default, the Galera Monitor will choose the node with the lowest
`wsrep_local_index` value as the master. This will mean that two MaxScales
running on different servers will choose the same server as the master.
### Galera clusters and slaves replicating from it
MaxScale 2.4.0 added support for slaves replicating off of Galera nodes. If a
non-Galera server monitored by galeramon is replicating from a Galera node also
monitored by galeramon, it will be assigned the `Slave, Running` status as long
as the replication works. This allows read-scaleout with Galera servers without
increasing the size of the Galera cluster.
## Configuration
A minimal configuration for a monitor requires a set of servers for monitoring