czw., 19 lip 2018 o 11:14 Willy Tarreau <[email protected]> napisał(a): > > Hi Milan, Janusz, > > I suspect I managed to reliably trigger the issue you were facing and > found a good explanation for it. It is caused by unprocessed bytes at > the end of the H1 stream. I manage to reproduce it if I chain two layers > of haproxy with the last one sending stats. It does not happen with a > single layer, so the scheduling matters a lot (I think it's important > that the final CRLF is present in the same response packet as the final > chunk). > > Could you please try the attached patch to see if you're on the same > issue ?
I've been running 1.8.12 with this patch for an hour. It seems that it helped somewhat, but not entirely. After an hour I still see about 10 CLOSE_WAIT sockets. The number seems to grow a lot slower, but still grows (and some of them have been sitting in CLOSE_WAIT for over 30 minutes). Since I'm also affected by SPDY_PROTOCOL_ERROR I mentioned earlier I must disable h2 now. -- Janusz Dziemidowicz
