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.
- Follow these general steps to upgrade your database. For detailed information about
each step, see your Upgrade Guide for performing an out-of-place upgrade.
- Disable rule saving.
- Migrate the PegaRULES schema to a temporary schema.
- Update the new rules schema, for example, a framework or application update.
- Copy the new rule schema to the production database.
- Upgrade half of the nodes one by one. For each node, do the following steps:
- Quiesce the node and remove it from the load balancer, following the instructions in To quiesce a node using immediate drain or To quiesce a node with slow drain, depending on your cluster configuration.
- Shut down the node.
- Configure the node to connect to the updated rules schema. For more information, see your Upgrade Guide for migrating the rules schema.
- Restart the node.
- Perform any needed post-upgrade activities and tests.
- Change the load balanced configuration to point to the upgraded nodes.
- Do step 2 for the remaining nodes, and then reactivate them in the load balancer.
- Quiesce behavior during high availability upgrades
If additional auto-generated rules were created after you created the export file for auto-generated rules during a high availability upgrade, users might see a server crash recovery message.
- Data management for upgrading and patching highly available systems
Follow Pega best practices for production data management to ensure successful upgrades and patches.
Previous topic High availability cluster settings Next topic Quiesce behavior during high availability upgrades