Scenario: Operational use of quiesce in a highly available system

Quiesce can be used operationally to address certain performance scenarios where redistributing users across Pega 7 Platform servers provides better consistency.

For this scenario, there are three Pega 7 Platform servers: A, B and C. In all scenarios, server C is the problematic server.

The following use cases illustrate the operational use of quiesce.

Move users from a failing or suspect Pega 7 Platform server

Pega 7 Platform server C has a proportional user load, but monitoring shows that it is exceeding CPU thresholds and response times are poor. Pega 7 Platform servers A and B are performing well within thresholds.

To add a replacement for Pega 7 Platform server C into the load balancer rotation, do the following:

1. Disable Pega 7 Platform server C in the load balancer.
2. Quiesce Pega 7 Platform server C.
3. When the state quiesce complete has been reached, diagnose the Pega 7 Platform server and perform corrective action.
4. Cancel Quiesce Pega 7 Platform server C or ensure that it has been restarted.
5. Enable Pega 7 Platform server C in the load balancer.

Balance users among a pool of Pega 7 Platform servers

Pega 7 Platform server C has over 60% of the total number of users. Operations wants to redistribute users to servers A and B.

To accomplish this, do the following:

1. Disable Pega 7 Platform server C in the load balancer.
2. Set the accelerated passivation timeout to a number that will gradually passivate users.
3. Quiesce Pega 7 Platform server C.
4. Observe the active user count until an acceptable number of users has been reached.
5. Cancel Quiesce Pega 7 Platform server C.
6. Enable Pega 7 Platform server C in the load balancer.

Related information

Open topic with navigation