Posted: 2 Feb 2018 10:13 EST Last activity: 4 Feb 2018 10:02 EST
System Pulse and need of pr_sysupdatescache in 731
We are upgrading from Pega 718 to Pega731. Upuntil Pega 718 we had a trigger in rules schema called TRPC_DATAADM which insert/update/delete rows in to pr_sys_updatescache table ( in work schema). I believe these rows are collected and processed by System Pulse agent.
From what we have seen in 731 media we dont have the trigger in DB anymore, so here are our questions
(0) Can we delete the TRPC_DATAADM trigger from our rules schema?
(1) Is pr_sys_updatescache obselete/deprecated from 731 and will it alway be empty?
(2)Will pr_sys_updatescache be empty/not used whether we are using database pulse or clusterbased pulse?
(3)[We are using ignite], if we decied to use clusterbased pulse can we STOP system pulse agents on all nodes/jvms
When using cluster based technology(hazelcast or ignite), the rule synchronization among nodes is taken care by these technologies.
System pulse will no longer be used by default to sync the rules in all nodes.
But, system pulse is required to identify whether a node is up and running i.e., every time system pulse agent runs, it updates the pyLastPulseDateTime in pr_sys_statusnodes table to indicate that a node is running.
For the clustering technology to work, it needs to know what are all the systems/nodes available to sync the rule changes. It knows from pr_sys_statusnodes table.
Here, system pulse is doing the job of updating the status of each node in pr_sys_statusnodes
So, system pulse is still required.
Yes, the table pr_sys_updatescache will be empty when using clustering based pulse(hazelcast/ignite).
Not sure what will be the implications if we delete the table pr_sys_updatescache table and as these are used when using ignite/hazelcast.
Others please reply.
I believe database triggers are not required in 7.3.1, please follow update guide instead of manually deleting triggers.