| 2016-10-20 20:37:49 |
Michael Johnson |
description |
Our API and CLI show the connection limit as '-1' which gets translated to not specifying a connection limit in the HAProxy configuration. When there is no connection limit specified in the HAProxy configuration it defaults to 2000 [1].
I think we should make the default 2000 and use that as the default instead of -1. There really isn't an "infinite" setting for HAProxy and setting it to 2000 means it is much less likely that the user will exhaust the amphora memory and cause the amphora to fail/failover.
[1] http://cbonte.github.io/haproxy-dconv/1.5/configuration.html#4.2-maxconn |
Our API and CLI show the connection limit as '-1' which gets translated to not specifying a connection limit in the HAProxy configuration. When there is no connection limit specified in the HAProxy configuration it defaults to 2000 [1].
We are incorrectly documenting -1 as infinite in the documentation.
I think we should make the default 2000 and use that as the default instead of -1. There really isn't an "infinite" setting for HAProxy and setting it to 2000 means it is much less likely that the user will exhaust the amphora memory and cause the amphora to fail/failover.
[1] http://cbonte.github.io/haproxy-dconv/1.5/configuration.html#4.2-maxconn |
|
