How to reproduce synchronisation issues between multiple nodes
We sometimes experience synchronisation issues. When adjusting rules on one node, the other node sometimes is not in sync. We cannot reproduce this behaviour at a specific time. Therefore we cannot raise an SR.
Question is, do you recognize this issue? And are you able to reproduce this. We are very curious about your experiences.
***Edited by Moderator: Pallavi to update platform capability tags***
Pegasystems Inc.
PL
Hi,
Let me ask a couple of questions:
1. What kind of clustering engine you are using to build the cluster?
2. What is the version of the PRPC?
3. This is on-prem or cloud installation?
4. Can you provide the logs where we can notice the issue?
Thanks,
Lukasz
Achmea
NL
Hi Lukasz,
1) We use Hazelcast.
2) 7.2.2
3) On-prem
4) That is the exact problem. We do not get log entries as far as we know, at least not at the time of problems occurring. What log entries should we look for?
Kind regards,
Rex
Pegasystems Inc.
US
Check the PegaCluster logs. It will show the members in the cluster. If you do not see all of your nodes in the member list, then a change on one node will not be able to reach the missing node.
Pegasystems Inc.
PL
Hi,
So as for the hazelcast configuration, please check it is correct. For the default, HC clustering is (prweb/WEB-INF/classes/prconfig.xml) :
<!-- Clustering -->
<!-- Hazelcast configs -->
<env name="identification/cluster/protocol" value="hazelcast" />
<env name="cluster/hazelcast/interface" value="<ip_address>" />
Where ip_address - You can also specify which network interfaces that Hazelcast should use. Servers mostly have more than one network interface so you may want to list the valid IPs. Range characters ('*' and '-') can be used for simplicity. So 10.3.10.*, for instance, refers to IPs between Proprietary information hidden and Proprietary information hidden. Interface Proprietary information hidden-18 refers to IPs between Proprietary information hidden and Proprietary information hidden (4 and 18 included).
And in prloggin.xml, put the below logging configuration (prweb/WEB-INF/classes/prlogging.xml):
<category name="com.hazelcast">
<priority value="ALL"/>
<appender-ref ref="<appender_name>"/>
</category>
Where appender_name - please specyfied the exsisting one or use below:
Hi,
So as for the hazelcast configuration, please check it is correct. For the default, HC clustering is (prweb/WEB-INF/classes/prconfig.xml) :
<!-- Clustering -->
<!-- Hazelcast configs -->
<env name="identification/cluster/protocol" value="hazelcast" />
<env name="cluster/hazelcast/interface" value="<ip_address>" />
Where ip_address - You can also specify which network interfaces that Hazelcast should use. Servers mostly have more than one network interface so you may want to list the valid IPs. Range characters ('*' and '-') can be used for simplicity. So 10.3.10.*, for instance, refers to IPs between Proprietary information hidden and Proprietary information hidden. Interface Proprietary information hidden-18 refers to IPs between Proprietary information hidden and Proprietary information hidden (4 and 18 included).
And in prloggin.xml, put the below logging configuration (prweb/WEB-INF/classes/prlogging.xml):
<category name="com.hazelcast">
<priority value="ALL"/>
<appender-ref ref="<appender_name>"/>
</category>
Where appender_name - please specyfied the exsisting one or use below:
<appender name="CLUSTER" class="com.pega.pegarules.priv.util.DailySizeRollingFileAppenderPega">
<param name="FileNamePattern" value="'<dir_to_logs>/PegaCLUSTER-'yyyy-MMM-dd'.log'"/>
<param name="MaxFileSize" value="50MB" />
<layout class="com.pega.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d [%20.20t] [%20.20X{tenantid}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n"/>
</layout>
</appender>
Wait until issue reoccur, and check the logs.
Thanks,
Lukasz