Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
Storage Execution
-
v7.0, v6.0, v5.0
-
Execution Team 2024-02-19
Description
Investigate the possibility of enabling concurrent capped writes using a special capped collection option allowConcurrentWrites:true for customers who prioritize capped collection size and throughput over maintaining consistent natural ordering across the replica set.
Attachments
Issue Links
- is related to
-
SERVER-82180 Capped inserts on the primary can have a different natural ordering from secondaries
-
- Backlog
-
-
SERVER-65261 Deleting from a capped collection via collection scan reports number of documents deleted incorrectly
-
- Closed
-
-
SERVER-16049 Replicate capped collection deletes explicitly
-
- Closed
-
-
SERVER-55512 Keep track of the next record to delete in capped collections
-
- Closed
-
- related to
-
SERVER-86266 remove MMAPv1 logic from RollbackViaRefetch code
-
- Needs Scheduling
-