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/MDSAL-212 mdsal <p>Given EOS and cluster-singleton-service are used and shard-leader for EOS is located on one cluster node and service-owner (elected by cluster-singleton-service) is on another cluster node.</p> <p>When node of service-owner is isolated then there is no notification sent from cluster-singleton-service to service-owner. Result is: service-owner remains active until cluster heal. When isolated node rejoins the cluster then the notification arrives and service is stopped. But this should have happened right after isolation step.</p> <p>Operating System: All<br/> Platform: All</p> MDSAL-212

Isolated node is not notified by EOS (when EOS leader is on different node)

Bug Resolved Done Tomas Cere Michal Rehak Wed, 7 Dec 2016 16:37:45 +0000 Fri, 9 Mar 2018 18:00:18 +0000 Tue, 14 Feb 2017 11:12:59 +0000 0 5 <p>Hi Michal,</p> <p>Can you also provide logs for this bug?</p> <p>Attachment local-eos-20161213.tgz has been added with description: eos-css broken scenario log</p> <p>Karaf logs:<br/> 1-10.25.2.11.data<br/> 2-10.25.2.12.data<br/> 3-10.25.2.13.data</p> <p>Isolation log:<br/> isolation.log</p> <p>Jolokia log:<br/> jolokia.log</p> <p>Merged karaf logs:<br/> local-eos-20161213.log</p> <p>Merged jolokia+isolation+service events:<br/> local-eos-20161213.overview</p> <p>(in order to see raw color sequences in human friendly form use less -R)</p> <p>will have to wait for January, no resource available</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/51621/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/51621/</a></p> <p>This seems to only happen when some other service managed by singleton service<br/> throws an unexpected/uncaught exception which seems to stop the shutdown of all other services. Once the cluster heals the singleton service may receive another ownershipChanged notification which makes it seem like the attempt to close only happens after cluster heal.</p> Blocks BGPCEP-601 Development External issue ID 7322 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02x07: