Forum Discussion
NimbostratusPool with Least Sessions LB Method having 2 Virtual Servers with different persistence methods
HI All,
I have a pool of web servers in which two types of traffic connects to. I have client traffic that I would like to persist with cookies, and I have internal web services traffic from other servers that requires source based persistance. I'd prefer not having these same systems in two different pools. I am considering using Least Sessions as the Load Balancing method, mostly to keep the internal web services traffic appropriately distributed. However, I am not sure what the effect will be on clients who come into this pool using a different virtual server that has cookie based persistence set? Will Least Sessions honor a cookie and distribute it appropriately if it come from a virtual server that is using cookie based persistence? Will it fall back to Round Robin Load Balancing for the first request from a client that does not have the cookie, but connects with the Virtual server that utilizes cookie based persistence?
Thanks in Advance,
Al
2 Replies
- Kevin_Stewart
Employee
Unless I'm misunderstanding your question, load balancing honors a persistent connection and Least Sessions (or any) server selection should only occur in the absence of a persistence record. Further, cookie persistence is, generally, based on the virtual server name, pool name, and then node/port. So a persistence cookie, if transmitted to another virtual server, should not affect that virtual server's persistence or load balancing process. 
What_Lies_Bene1Cirrostratus
^What Kevin said. Plus;
Where you are using Persistence a load balancing decision is made only on the initial connection, after that (unless using OneConnect) the load balancing decision is bypassed as long as the persistence record/cookie is valid.
As long as you specify the load balancing method as Least Connections Node (rather than Member, so the real servers membership of both Pools is taken into account) I think this would work just fine.
