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

listCollections should not require a MODE_S database lock

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.7.3
    • 3.7.6, 3.6.21
    • Catalog, Storage
    • None
    • Fully Compatible
    • ALL
    • v3.6
    • Storage NYC 2018-04-23

    Description

      Currently the listCollections command requires a MODE_S lock on the database it's run on. When any transaction is active on that database, it will generally have a MODE_IX lock on a collection. This will conflict with the MODE_S lock on the database, causing listCollections to block until the transaction is finished or aborted.

      It should be sufficient to have the MODE_IS lock on the database, as long as each collection is locked as its details are gathered.

      Attachments

        Issue Links

          Activity

            People

              geert.bosch@mongodb.com Geert Bosch
              geert.bosch@mongodb.com Geert Bosch
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: