Hi Chris,
On Thu, Mar 17, 2016 at 11:38:56PM +0000, Chris Warren wrote:
> We???re currently testing a patch which adds an ???initial-state up/down???
> option to each server (and the default-server option) - the default behaviour
> remains unchanged:
> https://github.com/beamly/haproxy-1.6/commit/9e7ad68a0c6582a38591eb27626fdb31bb5f8c18
>
> I???m wondering if this is something that could be considered for a future
> haproxy release?
Yes it will have to. It was evocated several times since 1.3, but each
time there was an existing way to achieve the same thing so it was not
implemented. Last time we almost did it was during the development of
the feature allowing to change a server's address on the CLI, because
we wanted to be able to create down servers that are enabled later. But
there were other priorities...
Now that you have running code it's probably time to document it and
merge it. A small comment, I noticed that you named the setting
"initial-state", but given that certain settings can change at runtime
I guess it's preferable to remove "initial" from the name, just like
we don't have "initial-weight" or so. Thus better call it "state". I'd
also like it to support "going-up" and "going-down" so that we keep
the current behaviour by default ("going-down") and can force all 3
other modes.
Thanks,
Willy
