Forum Discussion
NimbostratusMultiple stateless http requests route to same member server from any given client
We have an older F5 BigIP. Our application makes multiple http requests and stays on a member server. To replicate, I am notice when I refresh my browser the same member server is hit. My assumption was that, "Stateless" http requests from the same client would hop around to different member servers with each request.
The http connection is being opened and closed on each request and Persistance (Default and Fallback) is set to none.
Is this correct behavior?
5 Replies
hoolioCirrostratus
Hi David,
Take a look here for some tips:
SOL10430 - Causes of uneven traffic distribution across BIG-IP pool members https://support.f5.com/kb/en-us/solutions/public/10000/400/sol10430.html
Aaron
David_KrainesssThanks, I reviewed that link, but it does not help my specific issue. I am getting fairly even traffic distribution, We have 1000s of clients/theads and teh stats are fairly even.
My question is a given client thread seems to stick to a member server for a given period of time. Why does it not hop around?
- Think HTTP Keepalives.
- Kevin_Stewart
Employee
HTTP is stateless, but TCP really isn't, and that's what persistence gets stuck to in the absence of any other mechanisms. Depending on how soon you're doing it, hitting the refresh button in the browser will probably all happen within the same TCP session. Do you have keep-alives enabled? Is this HTTP 1.1 traffic?
- David_Krainesss
OK, thanks for the advice.
Apparently the close connection at the application layer is not actually closing the socket. We are using a Java client to Jetty.
When we added a connection close http header record, we now see each request hop around.
Thanks again!
