When processing a drop collection command in a replicated setting, the collection will no longer be removed immediately from the storage system. Instead, the collection will be renamed to a special system.drop.* name. The collection will no longer be visible to users and will eventually be removed when the commit point of the replica set advances past the optime of the drop collection oplog entry.
- depends on
-
SERVER-29273 Two Phase Drops: add list of drop-pending collections to ReplicationCoordinator
-
- Closed
-
-
-
- Closed
-
- is depended on by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-29649 Add startupWarning when a replset node is running with --nojournal but hasn't set writeConcernMajorityJournalDefault to false
-
- Closed
-
-
SERVER-29373 Two Phase Drops: Relax index namespace length constraint under non-mmapv1 storage engines when doing collection renames for two phase drops
-
- Closed
-
-
-
- Closed
-