Forum Discussion
per virtual-server-basis / per server-pool-basis
I'm looking for an info about how connections are handled and forwarded by ltm to pool members.
afaik ltm handles connections on a per virtual server basis, but some tests done show that this is not the behavior I had and I'm expecting to have.
My scenario is:
3 server pools in least connection (member)
N virtual server with these 3 server pools associated (destination pool is choosen by an iRule)
It seems connections are handled on a per server-pool-basis and not per virtual server.
Do you know if the behavior I'm expecting is possible and/or I have to configure something on the virtual server/ server pool side in order to obtain it?
thanks in advance
Yuri
1 Reply
- hoolio
Cirrostratus
Hi Yuri,
From the 10.2.0 online help, you can see the difference between least connections (member) and (node). Basically, member (IP:port) should be specific to the individual pool where node would take into account the connections that a node (IP only) has from any pool and any port. I thought that a member-based load balancing algorithm would be specific to a pool not a virtual server. If that's the case, I am not sure there is a way to have this done per virtual server + pool basis.
Least Connections (member): Specifies that the system passes a new connection to the node that has the least number of current connections in the pool. This method works best in environments where the servers or other equipment you are load balancing have similar capabilities. This is a dynamic load balancing method, distributing connections based on various aspects of real-time server performance analysis, such as the current number of connections per node or the fastest node response time.
Least Connections (node): Specifies that the system passes a new connection to the node that has the least number of current connections out of all pools of which a node is a member. This method works best in environments where the servers or other equipment you are load balancing have similar capabilities. This is a dynamic load balancing method, distributing connections based on various aspects of real-time server performance analysis, such as the number of current connections per node, or the fastest node response time.
Aaron
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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