LinkedIn
Copied!

Table of Contents

Quiescing nodes using immediate drain

Version:

Only available versions of this content are shown in the dropdown

Immediate drain for quiesce on a highly available system is the default method for quiescing a node. 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.
When using the immediate drain method to quiesce a node, any operator can access a quiesced server for root cause analysis or remediation, regardless of the operator's user role or privileges.

For a diagram that illustrates the on-premises quiesce flow for highly available systems when using immediate drain, see On-premises immediate drain quiesce flow.

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.

  1. Identify the Pega Platform node or nodes that you want to quiesce.

  2. Do either of the following:

    • In Admin Studio, click System System & nodes .
    • In Dev Studio, click Configure System High Availability HA Cluster Management .
  3. Select the check box next to the node or nodes that you want to quiesce.

  4. 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 cancel the quiesce process for the selected node or nodes, click Cancel Quiesce.
    • The node state might not change to Quiesce Complete until after the node has been removed from the load balancer in the following step.
  5. 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.

On-premises immediate drain quiesce flow

The following diagram illustrates the on-premises quiesce flow for highly available systems when using immediate drain.

Immediate drain quiesce flow
Quiescing a high availability node using immediate drain

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.