Question
Pega Pulse - Stale rule on a node
Hi,
What might be the possible reasons when a RAP file deployed on node1 , and very frequently we are facing issue the node 2 is not able to pick the latest deployed code.
Below are the options I have already tried
1) Cleared VT table, Application cache , rule cache
Below is the issue one of the issue we are facing, just an example
1) We have changed short description of the flow from X to Y
2) When user click on New/Create button from end user portal from node1, user is able to see the name of the flow as Y
3) On node2 , its still showing as X
Appreciate any thoughts?
Thanks,
Suman
***Edited by Moderator Marissa to update categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Please find the below details requested
1. Have you observed this behaviour on any rule types post-deployment on Node2? or specific to one rule?
Have observed for activitiy, flow, application and data page rules till date
2. What is the PRPC version ?
Pega 7.1.7
3. How did you deploy RAP file on Node1, using Import wizard or Command line ?
Using import wizard
4. Have you tried restarting the system pulse agent directly on SMA if it's a lower environment to validate this behaviour ?
Haven't tried will do that.
Thanks,
Suman
Hi Venkata,
You should also apply this prconfig setting. This setting is used by the pulse and helps ensure all of the records are processed when importing rules.
<env name="systempulse/scanoffsetms" value="60000" />
Carissa
Hi Venkata, we also facing the same is that worked ?
Hi Venkata,
As soon as you import, any updated rule gets updated in pr_sys_updatescache table with particular node-id in pzNodeName. So there should be an entry for this updated rule in this table with node1 reference. System pulse on node2 will take care of querying this table and updates it's local cache.
Need few details to get more clarity in here -
1. Have you observed this behaviour on any rule types post-deployment on Node2? or specific to one rule?
2. What is the PRPC version ?
3. How did you deploy RAP file on Node1, using Import wizard or Command line ?
4. Have you tried restarting the system pulse agent directly on SMA if it's a lower environment to validate this behaviour ?
BR//
Harish