I can isolate that to http2, not threads at v1.8.2 Separately, I am seeing a lot of intermittent failures with POST/PUT requests, I see the following returned from haproxy. <html><body><h1>400 Bad request</h1> Your browser sent an invalid request. </body></html>
I can verify these requests never hit the backend. On Thu, Dec 28, 2017 at 1:47 AM Robin Anil <robin.a...@gmail.com> 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. > > 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... > > My question is, is this a known behavior? Definitely not desired, not > unless the stats page has some indicator that update is happening and > connections are being migrated over or something. > > Robin >
