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
-
SERVER-29357 Two-Phase Drops: Document validators should be allowed in drop-pending collections
- Closed
- is depended on by
-
SERVER-29275 Two Phase Drops: implement collection drop commit logic
- Closed
-
SERVER-29280 Two Phase Drops: all drop-pending collections must be dropped immediately upon downgrade to 3.4
- Closed
-
SERVER-29459 Two Phase Drops: add option to listCollections command to include drop-pending collections
- Closed
- is related to
-
SERVER-20438 Oplog performance on primary: efficiency of uncommitedRecordIds
- Closed
-
SERVER-25860 Flatten / optimize fixup_info
- 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
-
SERVER-29374 Remove massert check on numIndexesInProgress() from IndexCatalog::dropAllIndexes()
- Closed