Forum Discussion

IslamAbulaynain's avatar
IslamAbulaynain
Icon for Nimbostratus rankNimbostratus
Feb 10, 2021

For the "Least sessions" Load Balancing method, is it a Member-based or a Node-Based?

The Least session member depends on the persistence table where each record is mentioned with its pool/pool member but the method definition mentioning that the node

 

And there is no member/node modes for this method

 

So how does it work? is it member-based "within the pool persistence records" or Node-based "checking the persistence records for the node across all pools"?

 

Thanks

application delivery
BIG-IP
LTM

2 Replies

Sort By
  • Aayush_Narayan's avatar
    Aayush_Narayan
    Icon for Nimbostratus rankNimbostratus
    Feb 10, 2021

    This load balancing method will simply make load balancing decision based on persistence record stored in the persistence table. Unlike least connection , we cannot modify load balancing mechanism to make decision based on pool member and node level.

     

    Can I know which definition are you referring to?

    Is it regarding the single node persistence?

     

    Thanks

    • IslamAbulaynain's avatar
      IslamAbulaynain
      Icon for Nimbostratus rankNimbostratus
      Feb 11, 2021

      This is the definition:

      Least Sessions: The system passes a new connection to the node that currently has the least number of persistent sessions. 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 sessions. Use of this load balancing method requires that the virtual server reference a type of persistence profile that tracks persistence connections.

       

      sorry for the conflict, the definition doesn't confirm if it is member or node based

      As you said "we cannot modify load balancing mechanism to make decision based on pool member and node level." ...So I think we still have the same question: does the LTM consider all persistence records for the node across all pools or within the same pool?