Skip to main content

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

Configuring nodes for high availability

Updated on July 8, 2022

The following list outlines the process that project managers should follow when creating a new highly available system using a Pega Platform installation.

  • Architecting a high availability system

    The Pega Platform supports production service level agreements and emphasizes redundancy as a best practice for physical and software-based highly available production architectures.

  • Cluster management

    A typical Pega Platform cluster consists of several physical or virtual machine instances sharing a single database. Machine instances may have multiple web application server instances or Pega Platform servers.

  • Performing a rolling upgrade

    You can upgrade Pega Platform by performing a rolling upgrade (rolling restart) that keeps your system available during the upgrade process. You remove nodes from the load balancer, shut them down, upgrade, and restart each node one by one. When you have upgraded half of the nodes, you add them back to the load balancer.

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