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

Remove two-phase database drops

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Replication
    • Repl 2024-06-24, Repl 2024-07-08

      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.

            Assignee:
            kishore.devireddy@mongodb.com Kishore Devireddy
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: