Hi guys,
I just noticed I had missed a timeout client.. When disabling that - I
can't seem to reproduce the 408 issue.
Willy Tarreau said the following on 02/20/2014 08:44 PM:
[CUT]
--- a/src/proto_http.c
+++ b/src/proto_http.c
@@ -2484,6 +2484,10 @@ int http_wait_for_request(struct session
We have experimented a bit with the latest haproxies and keep-alive. We
rely on haproxy to set good maxconn values for our servers so they can
operate at full speed without becoming overloaded.
When using multiple servers in a backend, prefer-last-server is required
to get keep-alive working, but
Sorry to plug my own piece of code here ... ExaProxy (on github) was designed
for that use.
However the documentation (or absence of) may discourage you ..
Thomas
On 3 Jan 2014, at 21:16, Lukas Tribus luky...@hotmail.com wrote:
Hi,
Hi, this question is silly, but I use haproxy even on my
Hello,
was it what the kernel change fixes ?
http://aleccolocco.blogspot.co.uk/2008/11/ephemeral-ports-problem-and-solution.html
Thomas
On 23 Feb 2014, at 11:45, Vincent Bernat ber...@luffy.cx wrote:
I am too lazy to find the first kernel which works. Looking at the
commits, I have found
Hi,
We have experimented a bit with the latest haproxies and keep-alive. We
rely on haproxy to set good maxconn values for our servers so they can
operate at full speed without becoming overloaded.
When using multiple servers in a backend, prefer-last-server is
required to get
Hi guys,
On Tue, Feb 25, 2014 at 02:13:32PM +0100, Lukas Tribus wrote:
Hi,
We have experimented a bit with the latest haproxies and keep-alive. We
rely on haproxy to set good maxconn values for our servers so they can
operate at full speed without becoming overloaded.
When
Slowly upgrading some load balancers with the latest snapshots, and we get
a lot of CL entries in our logs, this caused some people to get a bit
scared.
Typical tcp dump:
13:58:55.161381 IP x.x.x.x.39812 y.y.y.y.80: Flags [S], seq 1448645292,
win 5840, options [mss 1380,sackOK,TS val 231360268
Hi,
I just noticed I had missed a timeout client.. When disabling that - I
can't seem to reproduce the 408 issue.
Ok.
I applied both patches, and can still reproduce the error (when timeout
client is set), but the log no longer logs cR (since I enabled httplog).
I'm not sure if they are
I'm looking to release a new set of servers in the next month out so, and I'm
wondering if there are plans to release HAproxy with SSL support in a
production supported version any time soon?
I see there have been several updates to the current dev line since SSL was
released, so I'm keeping
On Tue, February 25, 2014 9:45 pm, Lukas Tribus wrote:
[CUT]
I'm not sure if they are useful if they are both applied at the same time.
The first patch enables additional logging via debug syslog, but the
second
patch may avoid that particular code path, if I understand correctly.
Sorry
10 matches
Mail list logo