nn balancing.
>
> The problem is that in this setting, leastconn applies within each backend
> and the selected server is not essentially the GLOBAL least loaded server in
> total (maybe due to a bug in the system).
It's not a bug, it's by design : haproxy doesn't know
this happen. But for me as new
user, it was complex to figure out what changes I need to do to fix this.
Any help is appreciated.
From: Baptiste
To: N P
Cc: "haproxy@formilux.org"
Sent: Tuesday, June 2, 2015 12:48 PM
Subject: Re: Global least loaded server
On Tue, Jun 2, 20
g.
>
> The problem is that in this setting, leastconn applies within each backend
> and the selected server is not essentially the GLOBAL least loaded server in
> total (maybe due to a bug in the system). Note that, same servers are used
> in the backends with different weights.
>
backend and
the selected server is not essentially the GLOBAL least loaded server in total
(maybe due to a bug in the system). Note that, same servers are used in the
backends with different weights.From what I understood from the code, the
problem seems to be that each backend tracks the number
4 matches
Mail list logo
