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

DistributedLock assumes that if a lock obj exists in the first config, then it is also true for others

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.8.0-rc5
    • Component/s: Sharding
    • None
    • ALL

      There are certain edge cases which can break this assumption, and the lock will be stuck in the state where it can never be acquired again without manual intervention.

            Assignee:
            Unassigned Unassigned
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: