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

Two Phase Drops: implement collection drop commit logic

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.5.8
    • Replication
    • None
    • Fully Compatible
    • Repl 2017-05-29

    Description

      Background: collections are no longer dropped immediately but renamed to a special drop-pending name and added to a task list in the ReplicationCoordinator.

      When the node sees the commit level (as dictated by the writeConcernMajorityJournalDefault) reach the drop op, it drops the drop-pending collection and removes the task from the list. Note that the proposed initial trigger for phase 2 (the drop op itself becomes known to be present on a majority of nodes) may not remain so in future versions; it may need to be delayed until a different condition.

      Attachments

        Issue Links

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              benety.goh@mongodb.com Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: