Bug #70267 mysqlfailover: Better integration with loadbalancers
Submitted: 7 Sep 2013 20:56 Modified: 10 Sep 2016 10:08
Reporter: Daniël van Eeden (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Utilities Severity:S4 (Feature request)
Version: OS:Any
Assigned to: CPU Architecture:Any

[7 Sep 2013 20:56] Daniël van Eeden 
Description:
The mysqlfailover utility should be enhanced to make it easier to integrate with a loadbalancer.

The loadbalancer should be notified that there was a failover and direct traffic to the new master.

This can be done by:
- Sending a notification to the loadbalancer (can already be done with a script)
- Changing some property (availability of a TCP port, contents of a database table) to make the address of the new master discoverable by the loadbalancer health check.
- Running the mysqlfailover utility on the loadbalancer.

The types of loadbalancers I'm thinking of are:
- F5 BigIP
- Linux LVS
- HAProxy
- Connector/J loadbalancing

If the loadbalancer is notified quickly then the failover might be completed earlier from a client perspective as it doesn't have to wait on the health check to run.

How to repeat:
See description

Suggested fix:
See description
[2 Nov 2015 13:14] Daniël van Eeden 
This could be used to let MySQL Router know about a topology switch
[10 Sep 2016 10:08] MySQL Verification Team 
Hello Daniël,

Thank you for the feature request!

Thanks,
Umesh