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-1482 controller <p>OwnershipService.registerCandidate method doesn't send notification for slave role. New registered candidate has state "unknown", so getting master or slave role is a change which has to be propagated.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1482

Missing notification request after registration

Bug Resolved Done Robert Varga Vaclav Demcak Fri, 5 Feb 2016 11:06:39 +0000 Thu, 18 Feb 2016 12:03:40 +0000 Thu, 18 Feb 2016 12:03:40 +0000 Beryllium clustering 0 2 <p>This essentially boils down to the API contract of EntityOwnershipService, which seems to imply that a EntityOwnershipListener is not notified of the current state of the entity.</p> <p>A user wishing to attach a candidate, has to synchronize around calls to registerListener(), which then has to be followed-up with getOwnershipState() within the same synchronized block. This lock has to be taken by the listener, too, to prevent races.</p> <p>The problem with the above solution is that getOwnershipState() is synchronous, with no upper bound on time. This makes using it in a constrained environment, such as Netty thread callback, a very risky proposition.</p> <p>master: <a href="https://git.opendaylight.org/gerrit/34179" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/34179</a></p> Blocks OPNFLWPLUG-593 Development External issue ID 5247 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02quf: