[MXS-2799] Stopping keepalived doesn't stop MaxScale Created: 2019-12-12 Updated: 2020-04-02 Resolved: 2020-04-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | ssauravy | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | HA | ||
| Environment: |
CentOS Linux release 7.6.1810 (Core) |
||
| Description |
|
Hi. -------------------------------------------------------- global_defs { script_user root enable_script_security }vrrp_script chk_maxscale { script "/usr/libexec/keepalived/is_maxscale_running.sh" #script "pidof maxscale" interval 2 # check every 2 seconds fall 2 # require 2 failures for KO rise 2 # require 2 successes for OK }vrrp_instance VI_1 { authentication { auth_type PASS auth_pass mypass }virtual_ipaddress { 192.168.100.10 }track_script { chk_maxscale } notify /usr/libexec/keepalived/notify_script.sh if [ "$grep1" ] && [ "$grep2" ] But There is a problem with the HA architecture. Please comment on this issue. |
| Comments |
| Comment by markus makela [ 2020-02-14 ] |
|
This does appear to be a limitation in the HA system if it is not configured correctly. You can use the PartOf systemd option to manage inter-process dependencies. This Stackoverflow post explains it nicely. This should be fixed by the addition of cooperative monitor locking in MaxScale 2.5.0. |
| Comment by Todd Stoffel (Inactive) [ 2020-04-02 ] |
|
Keepalived is a third party utility. We do not support custom bash scripts for that application. |