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
    • Epic Link:
    • 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

          depends on

          Task - A task that needs to be done. SERVER-29275 Two Phase Drops: implement collection drop commit logic

          • Major - P3 - Major loss of function.
          • Closed
          is documented by

          Task - A task that needs to be done. DOCS-10541 Docs for SERVER-29277: Two Phase Drops: implement dropDatabase changes to support 2-phase drops

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-29874 Two Phase Drops: dropDatabase does not work with applyOps

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-29876 Two Phase Drops: dropDatabase should always wait for pending collection drops to complete

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31436 dropDatabase must check `ReplicationCoordinator::canAcceptWritesFor` after reacquiring global lock

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32532 Two-phase dropDatabase may not replicate all collection drops before the database drop.

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-29913 bulk_api.js should use runCommand() rather than DBQuery().next()

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

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: