Re: Silencing DOWN alerts if the backend wasn't seen UP before

2016-02-12 Thread Willy Tarreau
On Thu, Feb 11, 2016 at 01:42:18PM -0800, Maciej Katafiasz wrote: > On 9 February 2016 at 23:24, Willy Tarreau wrote: > > I've got this request about 10 years ago, I wanted to implement a server > > option called "expect-down", then some users suggested that it could also > > be

Re: Silencing DOWN alerts if the backend wasn't seen UP before

2016-02-11 Thread Maciej Katafiasz
On 9 February 2016 at 23:24, Willy Tarreau wrote: > I've got this request about 10 years ago, I wanted to implement a server > option called "expect-down", then some users suggested that it could also > be convenient to have a "start-down" option which would not mark the > servers up

Silencing DOWN alerts if the backend wasn't seen UP before

2016-02-09 Thread Maciej Katafiasz
Hi, In our deployment we sometimes spin up a HAProxy container simultaneously with backends, and since they're registered the moment a container is spawned, they will be added to rotation immediately, before the process inside had a chance to start up. Because HAProxy starts up much faster, this

Re: Silencing DOWN alerts if the backend wasn't seen UP before

2016-02-09 Thread Willy Tarreau
Hi, On Tue, Feb 09, 2016 at 01:59:40PM -0800, Maciej Katafiasz wrote: > Hi, > > In our deployment we sometimes spin up a HAProxy container > simultaneously with backends, and since they're registered the moment > a container is spawned, they will be added to rotation immediately, > before the