Only setFCV should take the fcvLock (ResourceMutex) in exclusive mode

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.3
    • Affects Version/s: 3.7.1
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage 2018-02-26
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Also, all acquisitions of the fcvLock must invariant that !opCtx->lockState()->isLocked() before taking the lock, regardless of the mode. This is because the usage expectations around fcvLock is that it will always be taken before global/database/collection locks. This is to avoid deadlocks.

              Assignee:
              Dianna Hohensee (Inactive)
              Reporter:
              Esha Maharishi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: