Quiescing nodes using slow drain
Slow drain for quiesce on a highly available system is not the default. The following actions occur on a Pega Platform server when the quiesce process is enabled.
- The default time-out for passivation is reduced, referred to as an accelerated passivation period.
- Users are placed in a passivation queue.
- The system stops non-essential agent processing for quiesce and all listeners, with the exception of message-driven bean (MDB) listeners.
- When the active user requestor count drops to 0, the system sets the server state to "Quiesce Complete" and the Pega Platform server is ready for maintenance.
For a diagram that illustrates the on-premises quiesce flow for highly available systems when using slow drain, see On-premises slow drain quiesce flow
To quiesce a node with slow drain
The slow drain method requires removing the nodes from the load balancer before starting the quiesce process.
To quiesce a node with slow drain, do the following
steps:
- Identify the Pega Platform node or nodes that you want to quiesce.
- Configure the load balancer to disable the identified nodes. See your load balancer documentation for specific configuration instructions. Currently active users and services can complete their work, but no new connections can be made.
- Do either of the following:
- In Admin Studio, click .
- In Dev Studio, click .
- Select the check box in front of the node or nodes that you want to quiesce.
- Click Quiesce. When the quiesce process is complete, the status
of the node changes to Quiesce Complete in the Runstate or
State column on the landing page.
On-premises slow drain quiesce flow
The following diagram illustrates the on-premises quiesce flow for highly available systems when using slow drain.
Previous topic Quiescing nodes using immediate drain Next topic Moving applications between systems