Forum Discussion
sysadmin_2015_2
Nimbostratus
NimbostratusF5 Big-IP - Persistence Profiles
Hello,
We seem to be having an issue with Cookie based persistence profiles. The problem is during a code deploy, we split our traffic between two clusters of web servers, we put them in all in...
Is your proxy possibly re-using connections for multiple users? If so, you would need a one connect profile on the virtual server so that it load balances per request instead of per connection.
See https://support.f5.com/kb/en-us/solutions/public/7000/900/sol7964.html for more details
mimlo_61970
Cumulonimbus
CumulonimbusIs your proxy possibly re-using connections for multiple users? If so, you would need a one connect profile on the virtual server so that it load balances per request instead of per connection.
See https://support.f5.com/kb/en-us/solutions/public/7000/900/sol7964.html for more details
sysadmin_2015_2Hello, If OneConnect load balances per request and not connection, wouldn't the several requests made during a HTTP connection have more potential to land on a different server then? We would like uses that initially land on the new code to stay on the new code for the duration of their connection and same for users that initially land on the old code. Thank you,- mimlo_61970No, it still uses the persistence setting to keep them on the same server. The difference is without OneConnect, an LB decision is made once per TCP session. If the proxy is multiplexing multiple users through a single TCP session, the LB decision for all requests will be based off the first request. With OneConnect, the decision is per request, so if the proxy reuses the TCP connection for multiple users, the LTM will honor the persistence cookie in each request and make sure they land on the resource designated in the cookie.
- sysadmin_2015_2Hello, The OneConnect profile has resolved our issue. Thank you very much for the help! Thank you,
