Quiescing nodes with immediate drain
The default method for a quiescing a node is immediate drain, which does not require removing the nodes from the load balancer before starting the quiesce process.
The following behavior occurs on a Pega Platform server when the quiesce process is enabled.
- 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.
To quiesce a node using immediate drain
Quiescing a node with immediate drain does not require removing the nodes from the load balancer before starting the quiesce process.
To quiesce a node with immediate drain, do the following
steps.
- Identify the Pega Platform node or nodes that you want to quiesce.
- Do either of the following:
- In Admin Studio, click .
- In Dev Studio, click .
- Select the check box next to 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.
- To prevent traffic from being directed to the quiesced node or nodes, configure the load balancer to remove the quiecsed node or nodes from the pool.
Immediate drain quiesce flow
The following diagram illustrates the on-premises quiesce flow for highly available systems when using immediate drain.
Previous topic Quiescing high availability nodes Next topic Quiescing nodes with slow drain