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

Change default value of detect_standalone_master

Browse Source 
The default value was changed from false to true.
This commit is contained in:
Johan Wikman
2017-12-13 12:51:04 +02:00
parent 6d3e165bb0
commit b6e983c0b5
3 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Documentation/Monitors/MySQL-Monitor.md
View File

@ -139,8 +139,9 @@ External Server, Running` labels will instead get the `Master, Running` labels.
### `detect_standalone_master`
Detect standalone master servers. This feature takes a boolean parameter and is
disabled by default. In MaxScale 2.1.0, this parameter was called `failover`.
Detect standalone master servers. This feature takes a boolean parameter and
from MaxScale 2.2.1 onwards is enabled by default. Up until MaxScale 2.2.0 it
was disabled by default. In MaxScale 2.1.0, this parameter was called `failover`.
This parameter is intended to be used with simple, two node master-slave pairs
where the failure of the master can be resolved by "promoting" the slave as the

5
Documentation/Release-Notes/MaxScale-2.2.1-Release-Notes.md
View File

@ -37,6 +37,11 @@ root@host:~# maxscale --user=root ...
automatically enabled. In MaxScale 2.2.0, if `transaction_safety` was disabled
when `mariadb10_master_gtid` was enabled MaxScale would refuse to start.
### MySQL Monitor
The default value of the configuration parameter `detect_standalone_master` has
been changed from `false` to `true`.
## Dropped Features
## New Features