-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2017-05-29
With 2-phase drops, collections are not physically dropped (on all nodes) until the commit point advances past the optime when the collection drop was first requested on the primary. Since the ReplicationCoordinator maintains the commit point, it is a logical choice for a location to hold this list of drop-pending collections.
This list is updated when:
- At server startup, we scan all non-local databases for collections with a drop-pending namespace (see
SERVER-29251). - When processing a collection drop command in a replicated setting, we add the drop-pending namespace after renaming the collection and logging the drop request in the oplog.
- depends on
-
SERVER-29251 Two Phase Drops: add NamespaceString support for drop-pending collections
- Closed
- is depended on by
-
SERVER-29274 Two Phase Drops: rename collection to special drop-pending name
- Closed
-
SERVER-29275 Two Phase Drops: implement collection drop commit logic
- Closed