Thanks a lot, and sorry for my misinterpretation :-)
Cheers,
Federico
On Wed, 6 Feb 2019 at 14:59, Aleksandar Lazic wrote:
> Hi Federico.
>
> Am 06.02.2019 um 15:33 schrieb Federico Iezzi:
> > Hey there,
> >
> > Maybe this is gonna be a very simple answer.
> > In HAProxy 1.5.18 seems that the defaults maxconn have a global
> influence and not per backend one.
> >
> > In my case I have global maxconn at 5120001, while defaults at 256. What
> I'm trying to achieve is to set for all my backends the
> same maxconn without having the parameter everywhere.
> >
> > Testing it, I basically saturated the 256 connections right away and
> everything was queued. But that happened globally and not on a
> per-backend basis.
> >
> > Is that expected?
>
> Yes, AFAIK.
>
> Default/FE/Listen maxconn
> https://cbonte.github.io/haproxy-dconv/1.5/configuration.html#4-maxconn
>
> ```
> Fix the maximum number of concurrent connections on a frontend
> ...
> ```
>
> Backend maxconn is default 0
> https://cbonte.github.io/haproxy-dconv/1.5/configuration.html#5.2-maxconn
>
>
> ```
> ...
> The default value is "0" which means unlimited.
> ...
> ```
> > Thanks!
> > Federico
>
> Regards
> Aleks
>
