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

List Databases command should apply filter on name only before database locks

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.3, 3.5.4
    • Storage
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Storage 2017-03-06

    Description

      Right now, the listDatabases command checks for locks on each database (https://github.com/mongodb/mongo/blob/d7bd800d3d06004c4ca9114627ee882442e4d5e4/src/mongo/db/commands/list_databases.cpp#L129-L146) before actually checking the filter on the query (https://github.com/mongodb/mongo/blob/d7bd800d3d06004c4ca9114627ee882442e4d5e4/src/mongo/db/commands/list_databases.cpp#L148-L151).

      This means that if any user is doing a command that takes a lock on database a, (i.e. building an index), no one can run a listDatabase command, even if they've used a filter that should exclude database a.

      cc geert.bosch

      Attachments

        Activity

          People

            geert.bosch@mongodb.com Geert Bosch
            louisa.berger@mongodb.com Louisa Berger
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: