thanks for taking a look willy. let me know if there's anything else i
should change.

global
    maxconn 4096
    user haproxy
    group haproxy
    daemon
    log 127.0.0.1    local0 notice

# http
defaults
    log global
    retries    3
    timeout    connect 5000
    timeout    client  600000
    timeout    server  600000
    stats enable
    stats auth ggard:buddycat
    mode http
    option    httplog
    balance roundrobin
    # option httpclose
    option httpchk HEAD /check.txt HTTP/1.0

#stable sites run win2k/iis5/asp
listen stable 192.168.1.5:10301
    option forwardfor
    server stable1 192.168.1.10:10300 weight 4 check
    server stable2 192.168.1.11:10300 weight 6 check

# beta sites running mongrel/rails2.2.2
listen beta 192.168.1.5:8089
       server 7-8091  192.168.1.22:8091 weight 4 maxconn 1 check
       server 7-8092  192.168.1.22:8092 weight 4 maxconn 1 check
       server 7-8093  192.168.1.22:8093 weight 4 maxconn 1 check
       server 7-8094  192.168.1.22:8094 weight 4 maxconn 1 check
       server 7-8095  192.168.1.22:8095 weight 4 maxconn 1 check

       server 3-8091  192.168.1.23:8091 weight 6 maxconn 1 check
       server 3-8092  192.168.1.23:8092 weight 6 maxconn 1 check
       server 3-8093  192.168.1.23:8093 weight 6 maxconn 1 check
       server 3-8094  192.168.1.23:8094 weight 6 maxconn 1 check
       server 3-8095  192.168.1.23:8095 weight 6 maxconn 1 check







On Fri, Mar 6, 2009 at 4:51 PM, Willy Tarreau <w...@1wt.eu> wrote:

> Hi Greg,
>
> On Fri, Mar 06, 2009 at 03:54:13PM -0500, Greg Gard wrote:
> > hi willy and all,
> >
> > wondering if i can expect haproxy to queue requests when max conn per
> > backend it set to 1. running nginx > haproxy > mongrel/rails2.2.2.
>
> yes, it works fine and is even the recommended way of setting it for
> use with mongrel. There have been trouble in the past with some old
> versions, where a request could starve in the queue for too long.
> What version are you using ?
>
> > all seems ok, but i am getting a few users complaining of connection
> > problems and never see anything other than zeros in the
> > queue columns.
>
> Have you correctly set the "maxconn" on the "server" lines ? I suspect
> you have changed it in the frontend instead, which would be a disaster.
> Could you please post your configuration ?
>
> Regards,
> Willy
>
>


-- 
greg gard, psyd
www.carepaths.com

Reply via email to