Is Haproxy 2.0 default maxconn still enforced?

@m-a.leclercq wrote:

Hi everyone !

Quick question :
the facts
We are running haproxy 1.8 for the moment and are thinking of upgrading to Haproxy 2.0.7 but something is bugging me regarding the default maxconn.

haproxy -vv for 1.8 does display defaults : maxconn = 2000
however for haproxy 2.0.7 there is no default for maxconn.

We are migrating from 1.8 with nbproc 3 with a global maxconn at 1024 and no other explicit maxconn setting in haproxy.cfg to 2.0.7 with no nbproc setting and a maxconn at 4000 to compensate for the loss of 2 processes.

My question is the following : assuming I don’t want to limit any of my frontend/backend maxconn, is setting maxconn globally at 4000 enough for frontend and backends to inherit this setting or is the default maxconn = 2000 still present even though it is no longer reported by haproxy -vv ?

If this is still the case, that means I need to explicitly set maxconn to 4000 for every backend/frontend and it would make my configuration file quite redundant.

Willy’s comment at the bottom of this offical blog post is a little bit confusing to me with the release of Haproxy 2.0

Thank you for your help !

Posts: 1

Participants: 1

Read full topic