Last activity: 23 Feb 2016 22:00 EST
high availability in conjunction with load balancer (with 2 nodes behind the load balancer), do we really need to setup the load balancer with sticky session configuration?
We are actually going towards high availability direction.
1. Our production instance had load balancer with 2 nodes behind the load balancer.
2. When our internal team setup that load balancer, we requested them to setup with sticky session
4. Since we are going towards high availability, passivation setup set up in pega through (database/share didrive)
Someone told me that sticky session needs to be switch off, when we have the capability of passivation etc. on the pega side.
But my understanding is different that we need sticky session is needed basing on the articles i have gone through.
1. Can somebody confirm that sticky session in F5 load balancer is needed or not in conjunction with high availability?
2. Also it would be better to explain how they are tied together and the purpose technically