Production ruleset rule changes/checkin are not reflecting on all nodes in prodction
We delegated decision tables to production users and we noticed couple of times by now that when they check in changes did not reflect on all nodes, only on few nodes changes are synced.
We have 24 nodes in production
- Pega pulse is running on all nodes, then why this issue is happening and how to minimize this?
Client is asking why this is happening and is concerning business.
***Edited by Moderator Marissa to update Content Type from Discussion to Question***
Updated: 19 Mar 2020 13:43 EDT
Pegasystems Inc.
US
I see the tag mentions Pega 7.3. When you check the Pega cluster logs, do you see all of the nodes in the Hazelcast cluster?
Pegasystems Inc.
US
What about at the time the change was made to the delegated rule? If you check the PegaCLUSTER logs before and after that time frame, do you see any messages showing nodes leaving the cluster or a membership list? Since you mentioned that a few nodes were in sync with the change, it seems like an issue where Hazelcast could not communicate the change to all of the nodes.