You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 20, 2019. It is now read-only.
HAProxy 1.5 will have a neat feature that should us to do failover and elect a new Redis master when we do. This might allow us to get rid of downinter 365 which means that if both instances go down, HAProxy can elect the new master. (Whereas now, if both of them go down, it needs manual intervention)
Does it actually elect a new master, or just check to see who the current master is? I wonder how it works when one goes down, because I'm not too sure a node explicitly becomes master in that scenario (it's still slave, but just with a disconnected master)
Hey, turn that frown upside down. Maybe we can try Sentinel, it seems to at least be actively developed, and I think it's antirez who works on it. It has a bit more credibility than I originally thought with that big "experimental!" warning on it.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
app0> telnet proxy0 6379
Connection closed
cache0> telnet localhost 6379
Works fine
HAproxy is also no longer sending logs to syslog.
There are some nagios checks in #80 which monitor HAproxy's status
The text was updated successfully, but these errors were encountered: