Date: Tue, 24 Jun 2014 07:33:41 +0200
From: w...@1wt.eu
To: hapr...@stormcloud9.net
CC: haproxy@formilux.org; rachel.chave...@gmail.com
Subject: Re: 3rd regression : enough is enough!
Hi Patrick,
On Mon, Jun 23, 2014 at 09:30:11PM -0400, Patrick
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-06-24 01:33:41 EDT
*To: *Patrick Hemmer hapr...@stormcloud9.net
*CC: *haproxy@formilux.org, Rachel Chavez rachel.chave...@gmail.com
*Subject: *Re: 3rd regression : enough is enough!
Hi Patrick,
On Mon, Jun 23, 2014 at 09:30:11PM -0400, Patrick
...@gmail.com
*Subject: *RE: 3rd regression : enough is enough!
Date: Tue, 24 Jun 2014 07:33:41 +0200
From: w...@1wt.eu
To: hapr...@stormcloud9.net
CC: haproxy@formilux.org; rachel.chave...@gmail.com
Subject: Re: 3rd regression : enough is enough!
Hi
Hi guys,
today we got our 3rd regression caused by the client-side timeout changes
introduced in 1.5-dev25. And this one is a major one, causing FD leaks
and CPU spins when servers do not advertise a content-length and the
client does not respond to the FIN. And the worst of it, is I have no
*From: *Willy Tarreau w...@1wt.eu
*Sent: * 2014-06-23 10:23:44 EDT
*To: *haproxy@formilux.org
*CC: *Patrick Hemmer hapr...@stormcloud9.net, Rachel Chavez
rachel.chave...@gmail.com
*Subject: *3rd regression : enough is enough
Hi Patrick,
On Mon, Jun 23, 2014 at 09:30:11PM -0400, Patrick Hemmer wrote:
This is unfortunate. I'm guessing a lot of the issue was in ensuring the
client timeout was observed. Would it at least be possible to change the
response, so that even if the server timeout is what kills the request,
6 matches
Mail list logo
