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

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

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

      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@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: