-
Type:
Task
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
v7.0, v6.0, v5.0
-
Execution Team 2024-02-19, Execution Team 2024-03-04
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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.
- is related to
-
SERVER-65261 Deleting from a capped collection via collection scan reports number of documents deleted incorrectly
-
- Closed
-
-
-
- Closed
-
-
SERVER-16049 Replicate capped collection deletes explicitly
-
- Closed
-
-
-
- Blocked
-
-
SERVER-55512 Keep track of the next record to delete in capped collections
-
- Closed
-
- related to
-
-
- Closed
-