F5 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 one pool. We use ratio(member) based load balancing, Ratio 25 is set on the new code web servers with 75 set on the old code ones. 25% of production web traffic landing on the new code and the remaining 75% on the old code. We run this way for a couple of days to make sure there is nothing wrong with the new code before we send 100% traffic down it. We also set a persistent profile(cookie - session) on the virtual servers(80 and 443, we do an iRule redirect to 443). We do this because we want users that land on the new code to stay on the new code but they seem to be bouncing around.
What we think might be happening is during the several AJAX calls we make it throws users back out and in and then they have 75% chance landing on the old code? We use a proxy in front for security so we don't believe a source_address profile will work.
Where hoping someone could offer some insight to what the issue might be and how we can solve it?
Thank you for your help,
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