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/GENIUS-73 genius <p>Following up on an idea raised in <a href="https://jira.opendaylight.org/browse/GENIUS-62" title="lock-manager-impl floods logs with OptimisticLockFailedExceptions" class="issue-link" data-issue-key="GENIUS-62"><del>GENIUS-62</del></a> let's discuss and try whether we can use the EntityOwnershipService inside the lockmanager implementation to re-use an already existing cluster-wide exclusive locking mechanism? (Or if we determine we cannot, we could document here why not; or what gaps there are in EntityOwnershipService in order to be able to.)</p> <p>Operating System: All<br/> Platform: All</p> GENIUS-73

lockmanager based on EntityOwnershipService ?

Improvement Resolved Won't Do Unassigned Michael Vorburger Thu, 13 Apr 2017 11:34:51 +0000 Wed, 8 Jan 2020 05:21:34 +0000 Wed, 8 Jan 2020 05:21:34 +0000 (unspecified) General 0 2 <p>Thanks Michael for bringing this up.</p> <p>The main concern that I have is since LockManager exposes RPC's, the request will land only on one of the cluster nodes. So there is no point in using EntityOwnership unless there is something similar to Clustered listeners which ensures that the request reaches all the nodes.</p> <p>As Kency has commented, we need a cluster wide solution. Hence closing this</p> Development External issue ID 8224 External issue URL Issue Type Rank 0|i01oon: