On Thu, Dec 28, 2017 at 03:41:51AM -0600, Robin Anil wrote: > If the server is running in http2 mode, and servicing connections, updating > the config as shown below is no longer instantaneous. Takes over 5 minutes. > Even when the update is a no-op like adding a new line at the end of the > existing config. If the server is running in non http2 mode then any config > updates are near instantaneous > > haproxy -f new_haproxy.cfg -p haproxy.pid -sf $(cat haproxy.pid)
But how do you *measure* that it takes 5 minutes ? Is it the time it takes for the command above to complete and get back to the shell ? And if so, how are you sure that your changes were applied ? Sorry for insisting, but it's very important that we understand if it is more related to the config parsing, to the ability to take over some listening ports, or anything else. Willy
