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

Lock manager should expose methods that separate enqueuing a lock request and waiting for it to be satisfied

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 2.8.0-rc1
    • None
    • Concurrency
    • None
    • ALL

    Description

      To resolve SERVER-15310 in a race-free manner, it is necessary to enqueue a request for the global shared lock, then kill all outstanding operations, then wait for the lock request to be satisfied. This order is needed to prevent a race between killing outstanding operations and acquiring the global shared lock, during which a new operation might sneak in.

      Attachments

        Activity

          People

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            schwerin@mongodb.com Andy Schwerin
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: