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

proactively drop newly empty databases (sharding)

    XMLWordPrintableJSON

Details

    • Sharding EMEA

    Description

      in SERVER-33272 we made empty databases proactively vanish as soon as they become empty, but this only was noticeable on non-sharded replica sets.
      This ticket is to extend that behavior to sharding, so that when a config server knows that all collections in a database have been dropped, it can automatically drop such a database.

      Attachments

        Issue Links

          depends on

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-33272 The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-77281 Investigate removing use of the DatabaseHolder and/or dropDatabase oplog entry in the storage execution layer

          • Major - P3 - Major loss of function.
          • Backlog

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-33272 The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-sharding-emea Backlog - Sharding EMEA
              milkie@mongodb.com Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: