[GENIUS-73] lockmanager based on EntityOwnershipService ? Created: 13/Apr/17  Updated: 08/Jan/20  Resolved: 08/Jan/20

Status: Resolved
Project: genius
Component/s: General
Affects Version/s: (unspecified)
Fix Version/s: None

Type: Improvement
Reporter: Michael Vorburger Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


 Description   

Following up on an idea raised in GENIUS-62 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.)

 Comments   
Comment by Kency Kurian [ 15/Sep/17 ]

Thanks Michael for bringing this up.

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.

Comment by Hema Gopalakrishnan [ 08/Jan/20 ]

As Kency has commented, we need a cluster wide solution. Hence closing this

Generated at Wed Feb 07 19:59:50 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.