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

MXS-1446: Make failover_timeout configurable

Browse Source 
The time that MaxScale waits for a failover is now configurable.
This commit is contained in:
Markus Mäkelä
2017-09-26 14:13:24 +03:00
parent 4c6e7a0dbc
commit 316f792242
7 changed files with 61 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
Documentation/Monitors/Monitor-Common.md
View File

@ -115,6 +115,19 @@ If the script execution exceeds the configured timeout, it is stopped by sending
a SIGTERM signal to it. If the process does not stop, a SIGKILL signal will be
sent to it once the execution time is greater than twice the configured timeout.
### `failover_timeout`
The timeout for the cluster failover in seconds. The default value is 90
seconds.
If no successful failover takes place within the configured time period, a
message is logged and the failover functionality is disabled.
This parameter also controls how long a MaxScale instance that has transitioned
from passive to active will wait for a failover to take place after an apparent
loss of a master server. If no new master server is detected within the
configured time period, the failover will be initiated again.
### `events`
A list of event names which cause the script to be executed. If this option is not defined, all events cause the script to be executed. The list must contain a comma separated list of event names.