Re: Current solutions to the soft-restart-healthcheck-spread problem?

❦ 6 mars 2014 16:15 CET, Jonathan Matthews cont...@jpluscplusm.com : 1) On restart/reload/disabled-server-now-enabled-via-admin-interface, haproxy considers a server to be 1 health check away from going down, but considers it *initially* up. On reload, haproxy could wait for a whole round

Re: Current solutions to the soft-restart-healthcheck-spread problem?

Hi Vincent, On Fri, Mar 07, 2014 at 09:10:21AM +0100, Vincent Bernat wrote: ??? 6 mars 2014 16:15 CET, Jonathan Matthews cont...@jpluscplusm.com : 1) On restart/reload/disabled-server-now-enabled-via-admin-interface, haproxy considers a server to be 1 health check away from going down,

Current solutions to the soft-restart-healthcheck-spread problem?

Hi all - [ tl;dr How do you stop haproxy using failed backend servers immediately after reload? Haproxy devs, please consider implementing a consider-servers-initially-DOWN option! ] I wonder if people could outline how they're dealing with the combination of these two haproxy behaviours: 1) On

Re: Current solutions to the soft-restart-healthcheck-spread problem?

Hi Jonathan, On Thu, Mar 06, 2014 at 03:15:25PM +, Jonathan Matthews wrote: Hi all - [ tl;dr How do you stop haproxy using failed backend servers immediately after reload? Haproxy devs, please consider implementing a consider-servers-initially-DOWN option! ] I wonder if people could