That's because HAproxy does not detect instantly that a backend server is
down. You have to set the intervals.
On Tue, Jan 22, 2013 at 11:59 AM, Boris Epstein borepst...@gmail.comwrote:
Hello all,
I just configured a very primitive HAProxy installation on a CentOS 6
machine with the
Thanks Zachary!
Do you remember specifically which ones those would be?
On Tue, Jan 22, 2013 at 12:05 PM, Zachary Stern z...@enternewmedia.comwrote:
That's because HAproxy does not detect instantly that a backend server is
down. You have to set the intervals.
On Tue, Jan 22, 2013 at 11:59
Example config line:
server app1 6.6.6.6:80 check inter 30s fastinter 5s downinter 1s
If you look up those parameters, inter, fasterinter, and downinter, you
should have what you need. (Do look them up).
On Tue, Jan 22, 2013 at 12:07 PM, Boris Epstein borepst...@gmail.comwrote:
Thanks
Also, do look into haproxy stats. Makes it pretty easy to tell what
condition backends are in.
On Tue, Jan 22, 2013 at 12:14 PM, Zachary Stern z...@enternewmedia.comwrote:
Example config line:
server app1 6.6.6.6:80 check inter 30s fastinter 5s downinter 1s
If you look up those parameters,
Thanks. Just tired it - still doesn't seem to work for some reason.
By the way, thanks for those params - they are not listed even here:
http://code.google.com/p/haproxy-docs/w/list
I probably would've never guessed them if it wasn't for you.
Well, back to the drawing board, as they say:)
On 22 January 2013 17:31, Zachary Stern z...@enternewmedia.com wrote:
The params are listed in the HAproxy manual.
Boris, my params are not a magical fix to make haproxy instantly detect
downtime. As you can see, my interval is set to 30 seconds.
Please read the manual to understand how
6 matches
Mail list logo
