Le 17/12/2013 00:08, Willy Tarreau a écrit :
On Mon, Dec 16, 2013 at 10:46:39PM +0100, Willy Tarreau wrote:
For now, the only thing I've noticed is that when haproxy uses a
keep-alive timeout greater than the one on the backend, the connection
will stay in CLOSE_WAIT state until the haproxy timeout expires.
I'm not surprized, there's no analyzer on the response side to handle
the close. It will be completely handled when the connections are
attached to a dedicated analyzer but for now we don't have it. I'll
see if I can find an elegant quick solution to this without risking
to break things.
OK I finally implemented a very simple idle connection manager in the
stream interface. It's very basic but does the job fine, if an error
or close happens on the server side, it simply closes the connection
and unregisters it.
It's a bit cleaner :-)
Oh nice ! I didn't expect this so fast ;-)
It's applied it on my test server, I can confirm it works well, thanks !
--
Cyril Bonté
