Re: Is it possible to avoid 503 error when one backend server has down and health check hasn't been launched yet

2016-12-24 Thread Willy Tarreau
On Sat, Dec 24, 2016 at 05:16:53PM +, Patrick Hemmer wrote: > > On 2016/12/24 10:42, Alex.Chen wrote: > > for my scenario, i need to using "balance source" to keep the > > persistence of haproxy's balancing, I find that when one of my backend > > server (s1) has been killed, and if the next

Re: Is it possible to avoid 503 error when one backend server has down and health check hasn't been launched yet

2016-12-24 Thread Patrick Hemmer
On 2016/12/24 10:42, Alex.Chen wrote: > for my scenario, i need to using "balance source" to keep the > persistence of haproxy's balancing, I find that when one of my backend > server (s1) has been killed, and if the next round health check is > still not launched, then s1 is still be marked as

Is it possible to avoid 503 error when one backend server has down and health check hasn't been launched yet

2016-12-24 Thread Alex.Chen
for my scenario, i need to using "balance source" to keep the persistence of haproxy's balancing, I find that when one of my backend server (s1) has been killed, and if the next round health check is still not launched, then s1 is still be marked as UP. after 3 retries, the redispatch option does