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

Proactively close newly empty databases



    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Storage
    • None
    • Storage Execution
    • Fully Compatible
    • 0


      Currently, the kv engine does not check to see if a database is empty after a collection drop. Thus, empty databases can persist until mongod restarts (or the catalog is reloaded via replication rollback to stable timestamp). This situation is usually benign, but a database entry's presence does do one thing: it enforces that no other databases that are spelled the same but differ in capitalization can be created.
      Because recover-to-timestamp exists, it can result in some replica set nodes having a catalog entry for an empty database while other nodes do not have such an entry. This can result in the ability to crash secondary nodes that have an empty database entry that a primary node does not have - by attempting to create a database with a different case than the existing empty database entry.

      To fix this, we can check to see if a database is empty (i.e., no collection entries remain in the catalog) after a collection drop. If it is indeed empty, we can attempt to close the database by locking it in X mode and calling DatabaseHolder::close().


        Issue Links



              backlog-server-execution Backlog - Storage Execution Team
              gregory.wlodarek@mongodb.com Gregory Wlodarek
              0 Vote for this issue
              6 Start watching this issue