We are facing an issue in production where the newly deployed rule is getting picked up for one operator and not for the other. After some time, both operators get to use the same rule. We suspect that this is because of rule cache syncing not happening properly.
<env name="cluster/hazelcast/members" value="xx.x.xxx.*"/> <!-- optional list of IPs for other members in our cluster - can be a range or comma separated -->
You have to make sure that the above nodes are started serially(one by one) and not paralell to make sure that the hazelcast cluster is formed appropriately. You will also notice it in the PegaRULES logs the cluster details with hazelcast members with their IP address and ports