Skip to main content
LinkedIn
Copied!

Table of Contents

Quiescing nodes with 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 Immediate drain quiesce flow.

  • Quiescing a node with immediate drain

    The default quiesce method is immediate drain, which does not require removing the nodes from the load balancer before starting the quiesce process.

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us