On Tue, Feb 2, 2016 at 4:11 PM, David Birdsong <[email protected]> wrote:
> > > On Tue, Feb 2, 2016 at 7:09 PM Bryan Talbot <[email protected]> wrote: > >> On Tue, Feb 2, 2016 at 3:56 PM, David Birdsong <[email protected]> >> wrote: >> >>> Has nobody else run into this w/ consul? Given the plethora of tools >>> around consul and haproxy and templating, I know others are using reloads >>> to keep backend current, but the old haproxy PIDs stick around listening w/ >>> incorrect backends. >>> >> >> I'm not using consul but am using haproxy in a docker container and >> reloading when backend hosts change registrations. I haven't seen this >> issue. I run using haproxy-systemd-wrapper and HUP that process to reload. >> > > does that mean the wrapper ensures that an old process exits and forces if > it doesn't eventually? > I don't believe it forces children proxies to exit but does pass on selected signals (like HUP) to them. -Bryan
