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

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

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.7.1
    • 3.7.3
    • Storage
    • None
    • Fully Compatible
    • Storage 2018-02-26

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              dianna.hohensee@mongodb.com Dianna Hohensee
              esha.maharishi@mongodb.com Esha Maharishi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: