-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2017-05-29
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.
- depends on
-
SERVER-29273 Two Phase Drops: add list of drop-pending collections to ReplicationCoordinator
- Closed
-
SERVER-29274 Two Phase Drops: rename collection to special drop-pending name
- Closed
- is depended on by
-
SERVER-29277 Two Phase Drops: implement dropDatabase changes to support 2-phase drops
- Closed
- is related to
-
SERVER-20604 CSRS with protocol version 1 is slow when doing reads from secondaries
- Closed