On Sat, Oct 8, 2016 at 9:52 AM, vi...@abinnovative.com <
vi...@abinnovative.com> wrote:

> Hi All,
>
>     Thanks, I have changed the options like check port 22 rise falls
> retries re-dispatch etc.. nothing works.
>
> As my client utility is written in apache camel, so it is retrying 3 times
> min, I have only two nodes for the haproxy, so one node gets alternatively
> failure and the second retry by camel is getting success. but haproxy is
> not automatically switching to running node.
>
> Thanks
> Vijay
>
>
> On 08-10-2016 02:49 AM, Igor Cicimov wrote:
>
> On 8 Oct 2016 2:16 am, "Willy Tarreau" <w...@1wt.eu> wrote:
> >
> > Hi Igor,
> >
> > On Fri, Oct 07, 2016 at 08:41:12PM +1100, Igor Cicimov wrote:
> > > > Listen
> > > > ...
> > > > ...
> > > > Retries 3
> > > > Option redispatch
> > >
> > > Vijay, did you read Lukas's email? Did you do as he suggested? Without
> > > health check nothing will work, how do you expect for haproxy to know
> that
> > > a backend server is down?
> >
> > In fact with non-determinism LB algorithms (ie: round robin), the
> algorithm
> > takes care of avoiding the previous server during a retry (if there's no
> > stickiness of course). That's not rocket science, it just tries to
> improve
> > the situation before the server is detected as down. But that must not be
> > used as an excuse for avoiding checks.
> >
> > Cheers,
> > Willy
>
> Thanks Willy that makes sense ofcourse. I guess the OP has issue with the
> ftp server then like it is not really down from the haproxy point of view
> but not able to serve requests. Since we were not told what the issue is or
> how did he test the failover it is just an assumption. More detail
> inspection of the ftp server health when the issue occures might reveil
> something.
>
>
>
> --
> *Thanks*
> *Vijay*
>

I think some logs are in order Vijay :-) Can you please paste the relevant
lines of the failed and the consecutive successful request in haproxy? The
flags might tell us whats going on. Don't forget to obfuscate any sensitive
data.

Cheers,
Igor

Reply via email to