Active connections to pool members are unevenly distributed. The load balancing method is Least Connections (member). Priority Group Activation is disabled. What is a potential cause of the uneven traffic distribution?
In a BIG-IP environment, load balancing and persistence work together but serve different purposes. While a load balancing method like Least Connections attempts to distribute traffic based on current connection counts, a persistence profile overrides this logic for returning clients.
Persistence Overrides Load Balancing: When a persistence profile (such as Source Address or Cookie persistence) is applied to a Virtual Server, the BIG-IP system tracks which client was sent to which backend member.
Sticky Sessions: If a client with a valid persistence record returns, the BIG-IP will send that client to the same pool member it was previously assigned to, regardless of the load balancing algorithm ' s current preference.
Uneven Distribution: If certain clients generate significantly more traffic or stay connected longer than others, the persistence table will " lock " those high-volume flows to specific members, resulting in an uneven distribution of connections across the pool.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit