[SERVER-82863] Add support for the new capped collection option 'allowConcurrentWrites'. Created: 07/Nov/23 Updated: 06/Feb/24 |
|
| Status: | In Progress |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Benety Goh |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | storex-shortlist | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||||||||||
| Backport Requested: |
v7.0, v6.0, v5.0
|
||||||||||||||||||||||||||||
| Sprint: | Execution Team 2024-02-19 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| 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. |
| Comments |
| Comment by Suganthi Mani [ 01/Feb/24 ] |
|
We discussed 2 options:
I believe we reached an agreement on option #2, as it appears to be less risky, simpler, and avoids potential upgrade-downgrade issues. The only downside is that option #2 will affect all capped collections, and customers won't be able to pick and choose. However, this should be acceptable as we expect this only as work-around. It's worth nothing, these parameters should be undocumented. |
| Comment by Steven Vannelli [ 20/Nov/23 ] |
|
Moving to Open so that we prioritize this at the top of our backlog. Needs to be done before 4.4 EOL. |
| Comment by Suganthi Mani [ 07/Nov/23 ] |
|
alan.zheng@mongodb.com Is it feasible for the product to gather customer input to evaluate the value of this ticket? |