In the past I've used a ludicrously high setting on the primary for
rise, the number of health checks it has to pass before it's
considered to be up again.
It's definitely a hack, though that's not to say I haven't used it in
Oxford, London, UK
How about handling it on the backend. Setup your health checks on a different
port and forward that port with iptables to the actual health check. When you
fail over to the slave have some automation that detects that and shuts down
iptables on the master. When your ready to receive traffic
We are using HAProxy to check for MySQL availability and failing over to a
slave. Is it possible to stop HAProxy going back to the master once it is up?
We want that to happen after manual intervention.
DISCLAIMER: The information in this e-mail and any attachment is
Mail list logo