Hi, 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. Thank you, Adithya