High Availability configuration required to support Quiesce
The requirement is for High Availability configuration to support the Quiesce feature when using an F5 Load Balancer (LB).
Steps to Reproduce
Here’s the explanation for the reported behavior:
There are activities that can be implemented before and after a node enters the Quiesce state. These activities are defined in the CTI/CPM frameworks upon which the applications are built. No further action is required in this regard. Call processing should continue as expected.
According to the Pega7.2.2 High Availability Administration User Guide - 17 Quiesce
- When a node is placed in a Quiesce mode, all users (new and existing) are passivated immediately and the node can be removed from the load balancer at the same time. Existing active requestors that are locked are passivated at the end of the current interaction.
- Access to the quiescing node is allowed for all users until the node is removed from the load balancer.
– Active requestors can continue sessions on the quiescing node.
– New sessions can be created on the quiescing node.
– Requestor data is saved after each interaction and the requestor is removed from memory.
– For each new interaction, the saved requestor data is used to activate the session on the node selected by the load balancer.
Once the node is in quiesce mode, passivation occurs after every interaction.
For more information, refer to: https://community.pega.com/system/files/pdfs/High%20Availability%20Guide_1.pdf
0% found this useful