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

Two Phase Drops: implement dropDatabase changes to support 2-phase drops

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.10
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Repl 2017-06-19, Repl 2017-07-10

      Description

      Collection drops are deferred until commit point advances to or past optime of drop operation. For database drops, we wait until all the collection drops are committed. While we are waiting for the collection drops to be committed, any writes to the database will be rejected. While the collection drop oplog entries are written to the oplog before they enter the drop-pending state, the dropDatabase oplog entry is only written to the oplog when all the collection drops are committed.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: