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

Remove two-phase database drops

    XMLWordPrintable

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Storage
    • None

    Description

      The Database object class has no special state on it today except for the isDropPending flag used to prevent new collections from being created while waiting for all collections to be two-phased drop committed. We can eliminate the Database object entirely, potentially.

      In addition, we can remove the rollback logic for the dropDatabase oplog entry and the oplog entry itself entirely. The dropDatabase command will simply two-phase drop all collections contained in the database, with nothing further to do.

      This ticket depends on removing readConcernMajority=false.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              gregory.wlodarek@mongodb.com Gregory Wlodarek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: