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

Merge branch '2.2' into 2.3

Browse Source
This commit is contained in:
Markus Mäkelä
2018-10-16 11:10:48 +03:00
parent a2ef874fe6 c3cd119454
commit 20af9afb49
3 changed files with 99 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -110,7 +110,9 @@ If the `use_priority` option is set and a server is configured with the
master node is chosen. This requires the `disable_master_role_setting` to be
undefined or disabled. The server with the lowest positive value of _priority_
will be chosen as the master node when a replacement Galera node is promoted to
a master server inside MaxScale.
a master server inside MaxScale. If all candidate servers have the same
priority, the order of the servers in the `servers` parameter dictates which is
chosen as the master.
Nodes with a non-positive value (_priority_ <= 0) will never be chosen as the master. This allows
you to mark some servers as permanent slaves by assigning a non-positive value