Forum Discussion
Load balancing method specific decision
Thank you Paulius I test it, and really the status changes to
Unavailable (Enabled) - The pool member's connection limit has been reached
I configured two servers in the pool
server 1 - connection limit 2 | priority group 20
server 2 - connection limit 1 | priority group 10
What expected are two first connections will go to server 1
The following connection to server 2
When one connection in server one is disconnected, the next connection will go to server one again.
In my test, all the connections go to Server 1
*I disabled the persistence of src_ip
MaxMedov That is correct, I believe because you have your session open and the server is responding it will maintain your connection to it unless it doesn't respond which at that point you will establish a new connection which will balance you to the new pool member that is active because of priority group activation. As an example, if you have the connection limit set to 5 and users 1-5 come in forming a single connection the connection limit will be met and the next set of users will go to the next pool as long as the connection limit remains at the limitation of 5 connections, once the next connection limit is hit the next new connection will move to the next pool because it will now be active and available to receive these connections. In my opinion I wouldn't perform this priority group method and would simply configure least connection (node) as the balancing method and have all servers available in the pool so that you have all your available resources allowed from the beginning instead of the servers sitting and not handling any connections.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com