Hi Corey,
On Wed, Jun 25, 2014 at 01:26:25AM -0700, Corey Osman wrote:
> HI,
>
> I have noticed that when I restart/reload haproxy, haproxymarks the servers
> in the backends as up without ever checking them.
>
> So traffic is being sent to the backend server even while the backend server
> is actually down. This occurs until the first health check fails on the
> server and haproxy marks the server as down.
>
> I realize that changing the interval to something lower would mask this
> problem but I don?t want to flood my server with health checks.
>
> I would expect haproxy to treat the server as down until the health checks
> passes. (guilty until proven innocence). Again this is only upon
> restart/reload.
>
> I am wondering if this is an bug in haproxy or a configuration issue on my
> part. Is there something missing from my config?
Neither, it's the expected behaviour. Trying to send traffic to a server
for 1 second or so on startup is *much* less a trouble than sending traffic
to no server at all and disrupting the whole service.
There has been a discussion recently about adding the ability to decide whether
to start up or down for a server. I guess that the recent activities have masked
a bit this low-priority work.
Willy
