https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-1843 controller <p>This issue was observed in the process of netvirt development. When the configuration leader is taken down objects in the datastore fire DTCL events even though they were created long ago.</p> <p>Some more details on this here: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1567128#c9" class="external-link" target="_blank" rel="nofollow noopener">https://bugzilla.redhat.com/show_bug.cgi?id=1567128#c9</a></p> <p> </p> <p> </p> CONTROLLER-1843

Spurious mdsal events after leader taken down

Bug Medium Resolved Won't Do Josh Hershberg Josh Hershberg Mon, 25 Jun 2018 11:50:00 +0000 Mon, 25 Jun 2018 12:38:58 +0000 Mon, 25 Jun 2018 12:35:06 +0000 0 2 <p>I assume the DTCNs were fired on a different node which took over as leader. And I assume the DTCL is not a ClusteredDataTreeChangeListener in which case the DTCL is only notified on the leader. So when a new leader takes over, the DTCL is then registered which notifies of all initial data. Sounds like that's what you're seeing - if so, it's working as designed.</p> <p>Turns out this is not a bug at all. See Tom's comment</p> <p>Well that depends on how you look at it <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/> This part was always sticky and was implemented before the ClusteredDTCL was conceived. Since non-clustered DTCL ensures only one notification occurs in the clustered,  one could argue it should do the same for the initial pre-existing data update.</p> Development Rank 0|i03fwn: