Re: code.google.com haproxy-docs

Il 15/11/2013 00:28, Chris Burroughs ha scritto: A variety of nicely formatted mirrors of the docs used to be at: https://code.google.com/p/haproxy-docs But all such urls are now returng 403. I'm not sure if they are "official" or not, but does anyone know what happened to them? I use th

code.google.com haproxy-docs

A variety of nicely formatted mirrors of the docs used to be at: https://code.google.com/p/haproxy-docs But all such urls are now returng 403. I'm not sure if they are "official" or not, but does anyone know what happened to them?

Re: How do sticky tables work?

On 2013/11/13 22:27, Jeff Zellner wrote: Hi there fellow HAProxy users :) Please excuse me if this is in the docs, I looked through but didn't find anything definitive. How do sticky tables work with respect to backend servers changing? If we balance connections on source, and sticky on same --

Re: [PATCH v2] Add ability to select HASH function amongst (SDBM/DJB2/WT6) and optionally apply avalanche

Hi Bhaskar, On Thu, Nov 14, 2013 at 10:10:44AM -0500, Bhaskar Maddala wrote: > > Worse, when applying consistent hashing on that, only two servers > > got the load for several seconds, then two other ones. > > This is interesting. I did not do a time series distribution in my testing > and this

Re: [PATCH v2] Add ability to select HASH function amongst (SDBM/DJB2/WT6) and optionally apply avalanche

Thank you for your comments, Willy. > 1) "hash algorithm" => I realized that this naming is confusing > because it's used in conjunction with the balance algorithm. > In practice, both the terms "hash algorithm" or "hash function" > are used, with the latter being much more common. So I changed

Re: segfault in 1.5-dev19 when maxconn reached

Yes this work well with snapshot 20130707. Thanks 2013/11/14 Lukas Tribus > Hi! > > > > Hi, > > > > I'm using haproxy 1.5-dev19 on centos 6.4 (2.6.32-358.23.2.el6.x86_64). > > > > > > And when the maxconn value is reached, haproxy crashed . > > > > Log message : > > > > haproxy kernel: : hapr

Re: [PATCH v2] Add ability to select HASH function amongst (SDBM/DJB2/WT6) and optionally apply avalanche

Hi Bhaskar, OK I'm finally done with this. Having reviewed the existing code allowed me to change my mind on a few points. 1) "hash algorithm" => I realized that this naming is confusing because it's used in conjunction with the balance algorithm. In practice, both the terms "hash algorithm

RE: segfault in 1.5-dev19 when maxconn reached

Hi! > Hi,  >  > I'm using haproxy 1.5-dev19 on centos 6.4 (2.6.32-358.23.2.el6.x86_64).  >  >  > And when the maxconn value is reached, haproxy crashed .  >  > Log message :  >  > haproxy kernel: : haproxy[4487]: segfault at 2a8 ip 000'0004541a5  > sp 7fff8c0a8c80 error 4 in haproxy[4

segfault in 1.5-dev19 when maxconn reached

Hi, I'm using haproxy 1.5-dev19 on centos 6.4 (2.6.32-358.23.2.el6.x86_64). And when the maxconn value is reached, haproxy crashed . Log message : haproxy kernel: : haproxy[4487]: segfault at 2a8 ip 000'0004541a5 sp 7fff8c0a8c80 error 4 in haproxy[40+8] Exemple conf with lo

Re: [PATCH v2] Add ability to select HASH function amongst (SDBM/DJB2/WT6) and optionally apply avalanche

Hi Bhaskar, I noticed a mistake I'm going to fix. I was a bit bothered by the fact that we had to exclude the hash types from the LB_ALGO while setting a balance algorithm, and realized that the bits you reused for the hash method are themselves covered by BE_LB_ALGO, which is not appropriate sinc

Re: [PATCH] OPTIM: buffer: align the last output line of buffer_dump()

On 2013/11/14 15:24, Willy Tarreau wrote: Hi Godbach, On Thu, Nov 14, 2013 at 10:47:03AM +0800, Godbach wrote: Hi Willy, buffer_dump() in src/buffer.c is a usefull function to dump buffer to do debugging. However, the last output line should be aligned in a more readable way. Ah cool, thank