> On Sun, Dec 22, 2013 at 05:05:16PM -0500, Patrick Hemmer wrote: >> No. As I said, I want to disable the backend. >> http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#4.2-disabled > That doesn't really work for backends since they don't decide to get > traffic. At least if a config accepts to start with the "disabled" > keyword in a backend and this backend is referenced in a frontend, I > have no idea what it does behind the scenes. I'm not even sure the > backend is completely initialized.
Ah, ok. I can live with that :-) > What do you want to do exactly ? Do you just want to disable the > health checks ? It's unclear what result you're seeking in fact. I was just looking to disable backends without restarting the service. Nothing more. Nothing less. Currenly when I want to disable a backend I just update the config and reload haproxy. Not a big deal. Was just hoping that since frontends and servers could both be enabled/disabled through the socket, that backends could too. The reason why I don't want to disable individual servers is that we have an automated process which enables & disables servers. If a backend is disabled, then I don't want a server to automatically get enabled and start taking traffic. By disabling the backend, we prevent this scenario. > Willy Thank you -Patrick
