RE: NOSRV and retries

http mode:

127.0.0.1:58270 [30/Jun/2008:11:10:20.515] accounts accounts/<NOSRV> 0/5002/-1/-1/5002 503 212 - - sQ-- 73/73/73/0/0 0/72 "GET /current_accounts/all HTTP/1.0"

tcp mode:
127.0.0.1:51308 [30/Jun/2008:11:09:17.072] accounts accounts/<NOSRV> 5001/-1/5001 0 sQ 73/73/73/0/0 0/70

Here is my listen section:

listen accounts 127.0.0.1:9001

        balance roundrobin
        server acc0 127.0.0.1:4300 check inter 500 rise 1 fall 2 maxconn 1
        server acc1 127.0.0.1:4301 check inter 500 rise 1 fall 2 maxconn 1

I'm using ab with 80 concurrent connections, timeout connect of 5 secs. Basically trying to push to the edge of connection timeout and seeing if it redispatches, which does not seem to happen.

I'm not using persistence cookies.

> Date: Mon, 30 Jun 2008 10:37:05 +0200
> From: w#1wt.eu
> To: asim_s3000#hotmail.com
> CC: haproxy#formilux.org
> Subject: Re: NOSRV and retries
>
> Hi,
>
> On Sun, Jun 29, 2008 at 03:55:52PM +0100, asim s wrote:
> >
> > Hey
> >
> > I'm running benchmarks on apache -> haproxy -> thin/rails, to try and get a configuration working.
> >
> > The problem I am having is with 'option redispatch' and 'retries'.
> >
> > I will set the following
> >
> > option redispatch
> > retries 3
> > contimeout 5000
> >
> > Then running ab to benchmark. When it reaches the 5 sec contimeout rather than retrying it will say NOSRV and sQ in the log, and return a 502 error code.
> >
> > I'm using ver 1.3.15.2, in tcp mode, balance roundrobin and maxconn 1 on each thin/rails instance.
> >
> > I'm confused as to why its returning 502 errors rather than redispatching.
>
> I agree it's not expected.
>
> > Can anyone help?
>
> What load balancing algorithm do you use, and is there a persistence cookie ?
> Could you provide one complete log line (remove the IP addresses if you want) ?
>
> Regards,
> Willy
>

http://clk.atdmt.com/UKM/go/msnnkmgl0010000002ukm/direct/01/ Received on 2008/06/30 12:15