[MXS-1444] Expose REST-API for enabling/disabling failover behavior. Created: 2017-09-18 Updated: 2018-03-28 Resolved: 2017-10-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Johan Wikman | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Epic Link: | MaxScale MRM |
| Description |
|
It must be possible to disable the failover behaviour without having to shut down MaxScale. This is almost the same as the HA task of being able to turn MaxScale active/passive, but not quite. When MaxScale is passive, it executes no scripts, when the failover behaviour is disabled, MaxScale will not execute the failover script but will execute other scripts. This may mean that MaxScale needs to be explicitly aware of whether a script is a failover/switchover script. Which may be desirable anyway. |
| Comments |
| Comment by markus makela [ 2017-09-28 ] |
|
Discussion on this pointed towards allowing normal scripts to be executed even in passive mode and with failover disabled. Failover scripts would only be executed if MaxScale is active and failover is enabled. As the failover and failover_timeout parameters were added to the mysqlmon, they can be configured at runtime without stopping MaxScale. |
| Comment by markus makela [ 2017-10-02 ] |
|
As monitor parameters can be altered at run-time, disabling the failover is automatically implemented. |