Libraesva Load Balancer

Backend’s Maximum Connections Is Too Low

42 views June 21, 2018 giorgio 0


The dashboard shows a number of maximum connections lower than the available sessions in the Frontend or the total supported conections on Servers.


Although it seems odd, everything is normal. The maximum connection on the backend is a reference value to the proxy engine which hint when to consider the backup as “full” of connections, and it is safe to keep it to the default value (10% of the server configuration).

The upper limit  of  connections is determined by the maximum numbers of connections on servers (or when this is unlimited, by the number of connections accepted by the frontend). Additionally, if you set a minimum number of connections on the servers, you are declaring a dynamic limit which depends on the backend’s load. During normal workload (i.e. lower than the specified full connection value, which is 100 in the screenshot above), the number of connection to a server is well balanced between the minimum and the maximum connections. When there are exceptional workload (i.e. above the configured value), connection are chosen with a more direct approach to increase the throughput.

Was this helpful?