Question
Rule Cache issue in multi-node environment
We are running Pega 7.4 Marketing - NBAA App on tomcat server with Oracle DB, have about 40 nodes working in production. We deploy changes to Decision tables and proposition data required by business on daily basis.
Sporadically, we are seeing issues with older version of decision tables getting picked up on few nodes in production although the latest version exists on that node.
We believe this is due to a cache Sync issue, verified system pulse is running on all nodes and we have shell unix scripts validating the pulse is latest on each node.
Can anyone provide inputs as to how we can deal this? Thankyou!!
Hi Shushruth,
Can you please share us the Pega RULES log from the the nodes where you are seeing cache issues ? Also, specify the problematic decision table instances names. This issue requires in depth analysis to find the root cause. You can also create incident with Pega GCS to troubleshoot this issue further.
Request you to check the below things:-
1.)
Seems to be VTable cache issue.
Can you check if page passivation is disabled with below setting (by any chance):
<env "initialization/persistrequestor/usepagelevelpassivation" value="false" />
Page passivation improves performance for production systems that may have 50 or more simultaneously connected requestors
https://community.pega.com/sites/default/files/help_v718/concepts/concepts2/conceptspassivation.htm
Also, Please check: https://community.pega.com/support/support-articles/decision-table-returns-old-value
2.)
In addition to above, try re-validating the application or application rulesets where you are experiencing the cache issues.
Please let us know if it helps.
Warm Regards,
Venkat