- from a phone, xquz typoz On Dec 28, 2017 3:31 AM, "Willy Tarreau" <[email protected]> wrote:
Hi Robert, On Thu, Dec 28, 2017 at 07:47:03AM +0000, Robin Anil wrote: > In Http/2 mode with threads enabled, updating the config on a live serving > haproxy server takes several minutes. > > If I turn this off, the update of config is near instantaneous. I'm sorry but I don't understand what you call "this" above nor what you mean by "updating the config". 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) > The config change itself is just adding a newline in the file. So it feels > like haproxy is waiting for connections to close down or something... How do you proceed for the update and how do you measure this "time" ? For me "updating" means reloading, where a new process parses the new file. Since I hardly see how it could take time to parse a file in which you only added a few lines, it's unclear to me what exact problem you're facing. Could you maybe explain the steps you're taking and what you're observing ? Thanks, Willy
