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

listCollections should not require a MODE_S database lock

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.6, 3.6.21
    • Affects Version/s: 3.7.3
    • Component/s: Catalog, Storage
    • None
    • Fully Compatible
    • ALL
    • v3.6
    • Storage NYC 2018-04-23

      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.

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

              Created:
              Updated:
              Resolved: