I see, not only is the command stuck, the stats page does not load beyond
top header part and that state continues to persist for about 5-6 minutes.
Here is my configuration.
defaults
log global
mode http
compression algo gzip
compression type text/html text/plain text/css application/javascript
application/octet-stream application/json
option httplog
option dontlognull
option redispatch
option tcp-smart-accept
option tcp-smart-connect
option forwardfor
timeout check 5s
timeout client 50s
timeout tunnel 60000s
timeout connect 20s
timeout http-keep-alive 15s
timeout http-request 30s
timeout queue 20s
timeout server 50s
hash-balance-factor 125
balance hdr(Cookie)
hash-type consistent djb2
stats enable
stats hide-version
stats uri /statz
default-server inter 5s fall 3 rise 1
On Thu, Dec 28, 2017 at 4:27 AM Lukas Tribus <[email protected]> wrote:
> Hello,
>
>
> > 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.
>
> So what you are saying is that *the command* to reload haproxy takes 5
> minutes. I assume that within that timeframe, both old and new
> requests continue to be served.
>
> H2 timeouts are different than H1. Please share you configuration,
> especially everything timeout related. I assume "timeout client" is
> more than a few seconds in your configuration?
>
>
> You may want to lower "timeout client" and configure hard-stop-after
> according to your expectation:
>
> http://cbonte.github.io/haproxy-dconv/1.8/configuration.html#hard-stop-after
>
> The different timeout behavior in H2 is already documented:
>
> http://git.haproxy.org/?p=haproxy-1.8.git;a=commitdiff;h=75df9d7a7acb741e8413a6c2f3d6b6fe07b44bb8
>
>
>
> Regarding email threads, you can look for the post on mail-archive.org
> and hit that Reply-to button at the bottom (it will use the msg-id as
> in the in-reply-to header, at least in thunderbird) - or you use do it
> on your own, the msg-id of the email is at in the bottom line:
> https://www.mail-archive.com/[email protected]/
>
>
> lukas
>
