Re: global maxconn behaviour in haproxy2.0

2019-07-08 Thread Willy Tarreau
On Wed, Jul 03, 2019 at 01:30:52PM +, William Dauchy wrote: > On Wed, Jun 26, 2019 at 11:29:47AM +1000, Igor Cicimov wrote: > > Those maxconn values are per frontend so if your backend is referenced by > > two frontends you might end up with a limit of 2 x maxconn on the backend. > > Hence it i

Re: global maxconn behaviour in haproxy2.0

2019-07-03 Thread William Dauchy
On Wed, Jun 26, 2019 at 11:29:47AM +1000, Igor Cicimov wrote: > Those maxconn values are per frontend so if your backend is referenced by > two frontends you might end up with a limit of 2 x maxconn on the backend. > Hence it is recommended to set maxconn per server too to protect from > situation

Re: global maxconn behaviour in haproxy2.0

2019-06-25 Thread Igor Cicimov
Hi, On Wed, Jun 26, 2019 at 2:52 AM William Dauchy wrote: > Hello, > > Using haproxy2.0 we are seeing logs with connection number while reloading: > Proxy stopped (FE: 0 conns, BE: 549563 conns). > > while we have in our configuration: > global maxconn 262144 > defaults maxconn 262134 > > I