Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-15488

Add a way for determining distributed lock ownership

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.7.6
    • Component/s: Sharding
    • Cluster Scalability
    • Sharding 2 04/24/15

      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.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: