Hi Willy,
Le 05/12/2012 22:43, Willy Tarreau a écrit :
OK, I see. The health checks are causing too many time-wait sockets.
This issue was very recently fixed (in 1.5-dev14) as haproxy now closes
health check sockets with a TCP reset, thus avoiding the TIME_WAIT. I'm
pretty sure they're the one causing the issue as I've experienced a
similar one recently (reason why I fixed it :-)).
I have not backported this yet as I wanted to keep an observation period.
This week at work, one team upgraded to haproxy 1.4.23.
Their configuration embeds a proxy for rsyslog backends in TCP, with TCP
checks. Once upgraded, rsyslog started to log periodical errors :
"netstream session will be closed due to error" caused by TCP resets.
It's not necessarily a big issue but they're wondering if other TCP
services won't be affected. They'll check all of them soon.
Aside of their analysis, I wonder if it's possible to introduce a new
option "check-nolinger". This would let users choose one or the other
behaviour.
--
Cyril Bonté
