Identify duplicate/redundant data change events on warm restart/ cluster node role change

asked 2017-02-01 05:24:25 -0700

mahanare gravatar image

Hi All,

As I understand, every warm restart and cluster node role change triggers data change events for all data.

We would like to build a notification mechanism for changes in data through yang notifications but are worried that we keep sending duplicate notifications.

Is there a way to identify the data change events in a smart way so that I can skip the duplicate events for the purpose of generating yang notification.

Please advice me if there is an option or any ideas towards the same?

edit retag flag offensive close merge delete