Support Article

rule updated in a node is not reflecting in another



The user's infrastructure is set up in such a way that there are 2 nodes in Pega cluster. If a rule is updated in one node of cluster, then the other node in the cluster is not reflecting. Every time servers need to be restarted for the rule changes to reflect.

Error Messages

Not Applicable

Steps to Reproduce

  1. Login to node 1 of Pega cluster.
  2. Change a rule and save and logout.
  3. Login to node 2 of same Pega cluster.
  4. Look for the same rule and if the changes are reflected.

Root Cause

A defect or configuration issue in the operating environment. Though there are 2 nodes in Pega cluster, pr_sys_statusnodes table show only one node. These 2 nodes are in the system & sharing the same temp directory. hence the Pega system pulse is not distributing the rule updates to other members of the cluster. Server startup reflects this misconfiguration. There is only one member in Hazel cast cluster.


Make the following change to the operating environment:

Created individual Pega temporary directory which resulted 2 unique node IDs in pr_sys_statusnodes table. System pulse recognizes those 2 nodes in the Pega cluster and distributes the rule updates using Hazelcast.

Published March 1, 2017

Have a question? Get answers now.

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