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.

Recovering a node

Updated on March 11, 2021


This content applies to On-premises, Client-managed cloud and Pega Cloud environments

Restart a node that is unavailable by performing a node recovery procedure.

  1. Decommission the failed node:
    1. In the header of Dev Studio, click ConfigureDecisioningInfrastructureServices.
    2. Select the service with the failed node by clicking the corresponding tab.
    3. For the failed node, in the Execute list, select Decommission.
  2. Fix the root cause of the failure.
    For example: Replace failed hardware parts, or the entire node.
  3. Recover the data:
    • If the data was previously owned by the failed node and is available on replica nodes, delete the Cassandra commit log and data folders.
    • If the data was previously owned by the failed node and is not available on any replica node, perform data recovery from a backup file.
  4. Restart the node and add it back to the applicable service.
    For more information, see Enabling decision management services.
  5. Run the nodetool repair operation.
  6. Remove unused key ranges by running the nodetool cleanup operation on all decision management nodes.

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