Two Phase Drops: implement collection drop commit logic

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.5.8
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2017-05-29
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Benety Goh
              Reporter:
              Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: