Hi Lukas,
On 04/10/2017 18:57, Lukas Tribus wrote: > Hello Niels, > > > a restart means stopping haproxy - and after haproxy exited completely, > starting haproxy again. When that happens, haproxy immediately stops > listening to the sockets and then waits for existing connections to be > closed (you can accelerate that with hard-stop-after [1], but that's not > the point). > > So what you are seeing is expected behavior when RESTARTING. I am wondering if this is actually an expected behaviour and if maybe that restart/stop should just shutdown the process and its open connections. I have made the following tests: 1/ keep an open connection then do a restart will work correctly without waiting for existing connections to be closed. 2/ Keep an open connection then do a reload + a restart: will wait for existing connections to be closed. So if restart should wait for existing connections to terminate then 1/ should be fixed otherwise 2/ should be fixed. I think it makes more sense to say that restart will not wait for established connections. Otherwise there will be no difference between reload and restart unless there is something else am not aware of. If we need to fix 2/, a possible solution would be: - Set killmode to "control-group" rather than "mixed" (the current value) in systemd unit file. > > Seems to me you want RELOAD behavior instead, so RELOAD is what Ansible > should trigger when it detects a config change, no RESTART. > Agree -- Moemen MHEDHBI
