Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Quiescing high availability nodes

Suggest edit
Updated on April 5, 2022

Quiesce is a process for cleanly taking a Pega Platform node out of service for maintenance or other activities.

When a node is being quiesced, active users are migrated to an active node when the quiescing node is no longer available.

You can use the Pega API or high availability landing pages to quiesce a node. For more information about these management tools, see Cluster management.

Note: All Pega Platform nodes on a physical or virtual machine must be quiesced before you can perform maintenance on the machine.

Pega Platform offers two types of quiesce: immediate drain (the default), and slow drain. To switch the quiesce method to slow drain, change the value of the session/ha/quiesce/strategy setting in the prconfig.xml file to "slowDrain" and restart the node.

Quiesce a node by using one of the following procedures, depending on how your cluster is configured:

  • Quiescing nodes with immediate drain

    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.

  • Quiescing nodes with 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.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us