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

ListDatabases implementation can cause dropped dbs to reappear

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Internal Code
    • Storage Execution
    • ALL
    • 0

      It locks databases just to check if they are empty (where empty is defined as not having an NS file). This is unnecessary since it computes the size just before grabbing the lock. Additionally, if a DB is dropped after we get the list of dbs, but before we lock that database, the DB will be artificially resurrected.

      The second loop uses the hard coded size of 1 which seems incorrect since it is almost exclusively for dbs that are "empty".

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            mathias@mongodb.com Mathias Stearn
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: