Remove maxconn 5000 or add it to the docs

[mariusglauer]

Awesome library! We were struggling with load spikes in the past days and noticed timeouts. So we wanted to increase the maxconn setting. As the HAProxy statistics page only shows the global maxconn (we set it to 100000 via EXTRA_GLOBAL) we were wondering why only 5000 active connections were possible until we found this:

docker-flow-proxy/haproxy.cfg

Line 13 in ed0ef0c

maxconn 5000

It is documented nowhere that you need to set e.g. FRONTEND_EXTRA=maxconn 100000 change this. We assumed that setting the value in the global section would be enough but the default section seemed to override this.

[thomasjpfan]

This should be more clear in the documentation. I will add a note in the EXTRA_GLOBAL section. Does EXTRA_FRONTEND=maxconn 10000 solve your issue?

In general, haproxy needs both global and the frontend to be set. For example, if the global maxconn is set to 100000, and the default maxconn is not set. The frontend maxconn will still be set to 2000 (in haproxy 1.8.*).

[mariusglauer]

@thomasjpfan Thank you so much, that was fast! I can't say for sure that it's resolved, we did not have a load spike since I changed the setting. But I assume that was the problem, because when I saw the problem occur, HAProxy statistics page said "current conns = 5000".

I'll let you know when I am sure that this resolved my problem.

[thomasjpfan]

Since you have access to the admin panel, you can check global maxconn and frontend maxconn:

The upper boxed number is the global maxconn, the bottom boxed number is the frontend maxconn.

[mariusglauer]

I think, it worked: