per virtual-server-basis / per server-pool-basis

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