High availability configuration
Hello!
My team trying to use high availability features. We have a configured host with 2 websphere servers and http plugin. Prconfig of 2 prpc instances contains:
<env name="session/ha/Enabled" value="true"/>
<env name="initialization/persistrequestor/storage" value="database"/>
Test user is configured to use external authentication.
Load balancing is working good, user logs in to different nodes.
Steps to reproduce:
1. Log in to prpc instance using load balancer url
2. Open assignment in user portal
3. Quiesce node with mentioned user, wait for 'quiesce complete' status
4. Shut down websphere server with appropritate prpc instance
5. Do some action in user portal.
Result:
In a very rare case we have loading spinner and action completes in an expected way. Assignment stay opened. Looks like everything is ok, requestor moved to another node.
But mostly afler a very short spinner assignment closes, page refreshes to portal. If we try to open this assignment, we see that case locked by another requestor. Looks like new requestor created.
So, what is the correct configuation of HA? How to correctly move requestor to another node with no assignment closed?
Pegasystems Inc.
IN
Do you have session affinity maintained in loadbalancer ?
Go through below article if you need further information
https://docs-previous.pega.com/pega-731-high-availability-administration-guide
Pegasystems Inc.
IN
First thing you need to use shared storage for quiecsing and crash recovery to work effectively for high availability .
Please refer below help document here .
Once a user is passivated, the Pega 7 Platform clears the user’s session cookie and the quiesced Pega 7 Platform server responds to their next request with a redirect to the load balancer. The load balancer handles the redirected request by sending the user to a Pega 7 Platform server that is active in the load balancer pool. For details, see Cookie management.
Are you facing any errors/exception in the logs .
Thanks,
Arun