-
Type: New Feature
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Major Change
-
Execution Team 2021-02-08, Execution Team 2021-03-22, Execution Team 2021-04-05, Execution Team 2021-04-19, Execution Team 2021-05-03
-
(copied to CRM)
-
178
Rather than letting them be implicit in the capped collection logic when you insert documents at the front.
- depends on
-
SERVER-55156 Move capped collection responsibilities to the collection layer
- Closed
- is depended on by
-
SERVER-12293 initial sync of a capped collection can often fail if highly transient
- Backlog
-
SERVER-32827 Initial sync can fail when syncing a capped collection if the capped collection rolls over on the sync source
- Backlog
-
SERVER-56230 Check capped collection hashes across replica set members in FCV 5.0+
- Closed
-
SERVER-63339 Investigate enabling more data consistency checks for capped collections
- Closed
- is related to
-
SERVER-80302 capped_large_docs.js is not resilient to replication rollback
- Closed
-
SERVER-55411 Enable create_capped_collection*.js for incremental backups
- Closed
-
SERVER-56262 Fix _cappedFirstRecord usage for capped collections
- Closed
-
SERVER-52892 Perform capped deletes in the same WUOW as inserts
- Closed
-
SERVER-54890 Disable background validation and dbHash checks on capped collections in 4.4
- Closed
-
WT-6383 Key consistent checking should allow mixed mode timestamps
- Closed
- related to
-
SERVER-63813 Allow transactions and snapshot reads on capped collections
- Backlog
-
SERVER-82863 Add support for the new capped collection option 'allowConcurrentWrites'.
- Closed
-
SERVER-21512 Collection::insertDocuments should handle capped collections directly
- Closed
-
SERVER-30256 Expand testing for initial sync in capped collections
- Closed
-
SERVER-80423 Make the preImage document always available to OplogDeleteEntryArgs
- Closed