[SERVER-15488] Add a way for determining distributed lock ownership Created: 01/Oct/14  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.7.6
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: AdiZ
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Cluster Scalability
Sprint: Sharding 2 04/24/15
Participants:

 Description   

The closest method in master (55097afd011278c9274b778a2bce45b170ba2bab) is DistributedLock::isLockHeld. Which only answers the question whether the lock is held. It also tries to check that the lock is associated with the lock object, but the granularity is at process level so the guarantee that it actually owns it is weak.


Generated at Thu Feb 08 03:38:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.