Hello,

2018-07-25 10:20 GMT+02:00 Willy Tarreau <w...@1wt.eu>:

> Hi Milan,
>
> On Wed, Jul 25, 2018 at 10:15:50AM +0200, Milan Petruzelka wrote:
> > Now I'll add both patches (WIP-h2 and h2-error.diff) and give it a try in
> > production.
>
> Thank you. At first I thought you still had the errors with them applied
> and was despeared, now I understand there's still hope :-)
>
> Cheers,
> Willy
>


It seems I have the same issue as Milan :
We activated HTTP/2 on production a few weeks ago, and on some customers
(not all !) we can observe a very strange behaviour : it seems some
frontend sessions are not closed, leading to 'slim' reached if HAProxy runs
for several days without being reloaded.

What can be observed:
- on a specific frontend, scur keeps growing over and over.
- reloading haproxy (with -sf parameter) clears sessions connected
- it happens only on specific frontends, but I failed to cross info (we
have issue on 2 frontends, both have reasonable trafic, but some frontends
with much more do not have the issue).
- disabling HTTP/2 solve the problem for these specific frontends, so this
is definitely HTTP/2 related

I ran several "show fd" and "show sess" on haproxy process, and filter it
with the frontend name. Both shows different number of lines, and the
difference is growing over time.

I am running HAProxy 1.8.12 with OpenSSL 1.1.0h compiled statically.

Here is one fd with the issue:
     58 : st=0x25(R:PrA W:pRa) ev=0x00(heopi) [nlc] cache=0 owner=0x46ceeb0
iocb=0x530c20(conn_fd_handler) tmask=0x1 umask=0x0 cflg=0x80201300
fe=xxxx:443 mux=H2 mux_ctx=0x45e27e0

With "flag" debug binary I debugged cflg and all "lost" sessions are in
this state :
conn->flags = CO_FL_XPRT_TRACKED | CO_FL_CONNECTED | CO_FL_ADDR_FROM_SET |
CO_FL_XPRT_READY | CO_FL_CTRL_READY

This issue is very close to Milan bug, that's why I posted as a reply. If
I'm wrong, I'll split it in another thread.

Willy, are your patches "production-safe" (meaning it is reasonable enough
to run it a few hours in production) ? Can it be applied on 1.8.12 release,
or do I need to download latest trunk ?

I can reproduce the issue quickly (~ 2 hours to be sure) on my side to help
!

Olivier

Reply via email to