On Sun, Apr 24, 2016 at 11:10:06PM +0200, Nenad Merdanovic wrote:
> This is very useful in complex architecture systems where HAproxy
> is balancing DB connections for example. We want to keep the maxconn
> high in order to avoid issues with queueing on the LB level when
> there is slowness on anot
This is very useful in complex architecture systems where HAproxy
is balancing DB connections for example. We want to keep the maxconn
high in order to avoid issues with queueing on the LB level when
there is slowness on another part of the system. Example is a case of
an architecture where each th
On Wed, Apr 20, 2016 at 10:16:24AM -0400, Nenad Merdanovic wrote:
> > At least I'd have found it more natural to use "10c" than "10m" to specific
> > a connection limit but anyway that's still something we might regret over
> > the long term. Thus, what do you think about using a completely differe
Hey Willy,
On 4/19/2016 12:24 PM, Willy Tarreau wrote:
>
> Your patch looks fine but I'm a bit bothered by the choice of the syntax
> here which is neither really intuitive nor future-proof. I even suspect
> you had some head-scratching before coming to this.
That was the hardest part actually :
Hi Nenad,
On Sun, Apr 17, 2016 at 12:05:04AM +0200, Nenad Merdanovic wrote:
> This is very useful in complex architecture systems where HAproxy
> is balancing DB connections for example. We want to keep the maxconn
> high in order to avoid issues with queueing on the LB level when
> there is slown
This is very useful in complex architecture systems where HAproxy
is balancing DB connections for example. We want to keep the maxconn
high in order to avoid issues with queueing on the LB level when
there is slowness on another part of the system. Example is a case of
an architecture where each th
6 matches
Mail list logo
