[MXS-603] Adding extra failover options to server configuration Created: 2016-03-05  Updated: 2017-12-01  Resolved: 2016-10-17

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: None
Fix Version/s: N/A

Type: New Feature Priority: Major
Reporter: VAROQUI Stephane Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None


 Description   

Following Master Slave failover blog from S9 it would be nice to take into account the lack of maxscale features exposed vs MHA

See http://severalnines.com/blog/mysql-replication-failover-maxscale-vs-mha-part-3

failover_candidate_master default 1
failover_failback_delay default 120 sec
failover_slave_lag_delay default 120 sec
failover_http_extra_check_script default http://127.0.0.1:8080/$server/status

this 8080 port would be a local http maxscale listener and that report 404 error when node failed
This would enable multiple maxscale to act against split brain



 Comments   
Comment by Johan Wikman [ 2016-03-07 ]

Seems like a sensible thing to do and does not seem to be that laborious either. However, this is better characterized as an improvement and not a bug.

Comment by markus makela [ 2016-10-17 ]

Doing this with some external actor, e.g. replication-manager, would be an better idea.

Generated at Thu Feb 08 04:00:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.