Yeah, I have Affinity turned on and I can explain the basic process.
We use sessions on the servers but nothing else. The session key is used on the server in order to validate a hash key each user gets when they login. This is a temporary key and with it we’re able to determine what database they are accessing and who they are.
Each server has a path file that goes with it to provide its unique domain name. This is where the first step of the problem comes in because we can’t turn on the load balancer without telling each server that they are part of the load balancer domain. Once you do this, you can’t access the servers directly. So they are either part of the load balancer or not.
So a user logs in to load balancer, they get pointed to specific server. That server then knows to direct any calls back through the load balancer which should identify the IP of client and send back to this same server. This seems to be working as I can login and go about my business without missing a beat. However, when things start to get a little loaded, all of the sudden people start getting logged out. The only thing I can think of is that the load balancer has all the sudden decided they should be sent to server 2 instead of server 1 and that server has no active session running and logs them out.
This is totally random but the tickets start coming in quickly. Another complaint we get almost immediately upon turning on the load balancer is how slow everything has started responding. I don’t see this on my end but every customer to a T opened tickets about it and the ones I spoke to commented about it even before they had any real issues.
So we appear to have 2 separate issues with the load balancer and not real sure what we can do about it. Testing it requires me to turn it on and turning it on means all of my customers are going to be upset with me within a few minutes.