On Tue, Aug 7, 2012 at 4:44 PM, Baptiste <[email protected]> wrote: > Hi, > > If you have enabled minconn, it's an expected behavior :) > otherwise, sharing your conf, screenshot and haproxy version would help a > lot.
Sorry for that, yep, we're using minconn (don't ask me why, I did not set it up) and maxconn to not overload the backends, and requests are only queued per LB not per backend. our $fullconn is the sum of all $maxconn's: listen dawanda_cluster *:8700 option httpchk GET /home/alive option httpclose balance roundrobin fullconn 361 server c5 192.168.2.25:8888 weight 1 minconn 4 maxconn 15 check inter 10000 server app2 192.168.3.2:8888 weight 1 minconn 4 maxconn 8 check inter 10000 server app3 192.168.3.3:8888 weight 1 minconn 4 maxconn 8 check inter 10000 server app5 192.168.3.5:8888 weight 1 minconn 4 maxconn 12 check inter 10000 server app6 192.168.3.6:8888 weight 1 minconn 4 maxconn 12 check inter 10000 server app11 192.168.3.11:8888 weight 1 minconn 4 maxconn 12 check inter 10000 server app16 192.168.3.16:8888 weight 1 minconn 4 maxconn 12 check inter 10000 server app17 192.168.3.17:8888 weight 1 minconn 4 maxconn 12 check inter 10000 server app31 192.168.3.31:8888 weight 1 minconn 4 maxconn 30 check inter 10000 server app32 192.168.3.32:8888 weight 1 minconn 4 maxconn 30 check inter 10000 server app33 192.168.3.33:8888 weight 1 minconn 4 maxconn 30 check inter 10000 server app35 192.168.3.35:8888 weight 1 minconn 4 maxconn 30 check inter 10000 server app36 192.168.3.36:8888 weight 1 minconn 4 maxconn 30 check inter 10000 server app37 192.168.3.37:8888 weight 1 minconn 4 maxconn 30 check inter 10000 server app50 10.10.40.9:8888 weight 1 minconn 4 maxconn 30 check inter 10000 server app51 10.10.40.10:8888 weight 1 minconn 4 maxconn 30 check inter 10000 server app52 10.10.40.5:8888 weight 1 minconn 4 maxconn 30 check inter 10000 Regards, Christian.
