Am 28.06.19 um 15:09 schrieb Максим Куприянов:
> Hi!
> I found out that in some situations under high rate of incoming connections
> haproxy=2.0.1 starts leaking sockets. It looks like haproxy doesn't close
> connections to its backends after request is finished (FIN received from
> client) thus leaving its server-sockets in close-wait state.

I believe your report might be a duplicate of this issue in the
bugtracker on GitHub, can you check:

Best regards
Tim Düsterhus

Reply via email to