I have 3 servers which i have to put behind balancer for load distribution. So i have configured a http virtual server (with cookie persistence).
Users can access services provided by these servers both through web browsers (when they are inside corporate) and also through api calls (when they are outside of corporate network).
The problem is when i direct outside users (i mean users which accessing via api calls via internet) traffics to the virtual server, the load distribution will uneven and always one of my pool memebers gets much more connection and requests from the other pool members, but for internal users everything is perfect.
I looked around and didn't get any results. my only guess is that the API requests would have to be balanced differently, but How?
I was wondering if anyone has had this experience?
Thank you for your guidance.
Solved! Go to Solution.
@Daniel_Wolf has a fair point to consider here,
If your application only ever keeps one connection open or is always from one IP persistance will lock that user to one location and wont release it until the connection times out. A company of many users behind a NAT/Proxy normally cause this issue. I know this is the advantage of cookie persistance, but API client don't normally use this.
How are you managing internal and external comms? One VS for each or a VS for external and internal?
Potentially you could put them onto different Virtual servers to try to put different persistance on each config. Maybe even check that youir fallback persistence profile is also set so if cookies aren't set you still have something.
Load Balancing is on the pool config so i think i'd leave that alone, i'd also keep away from having more than one pool with the same pool members in it otherwise you wont see the total picture.