Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

Managing your high availability cluster

Updated on April 5, 2022

The HA Cluster Management page details the current status of any nodes running in high availability mode and is used to perform quiesce actions for a node.

Operators with the following roles can access this page:

  • PegaRULES:HighAvailabilityAdministrator
  • PegaRULES:HighAvailabilityQuiesceInvestigator

You can access this page from Dev Studio by clicking ConfigureSystemHigh AvailabilityHA Cluster Management.

Note: Data is accurate after two system pulse cycles.

The following data is displayed on this page for each node.

NodeThe name of the node
NodeIDThe node ID
Runstate The status of the node:
  • Running
  • Stopped
  • Quiesce Complete
  • Quiesce Start
Active UsersThe number of active users
Last PulseThe date and time of the last system pulse
Last StartedThe date and time that the node was last started

To perform an action on any of the nodes listed on this page, select the check box next to the node(s) and then click one of the following buttons:

  • Quiesce – Begin the quiesce process for the selected node(s).
    Note: When using the slow drain method for quiesce, you must take the node(s) out of the load balancer rotation before performing this action.
  • Cancel Quiesce – Cancel the quiesce process for the selected node(s).
  • Refresh Data – Refresh the node data listed on the page.
  • Managing the cluster using the Pega API

    You can use the Pega API to integrate Pega Platform high availability into a Network Operations Center (NOC). The Pega API provides RESTAPIs for managing quiesce and other operations.

  • Quiescing high availability nodes

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

  • Previous topic Creating database instances by inheriting from an existing connection
  • Next topic Managing the cluster using the Pega API

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us