[SERVER-74430] Long-running writes do not wait for writeConcern until they complete Created: 28/Feb/23 Updated: 05/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | or-workload-management | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Participants: | |||||
| Description |
|
Writes only wait for writeConcern after they finish. This means that large multi:true updates or deletes can replicate unthrottled until they finish. This can engage flow control, but because it is quite agressive, this negatively impacts other writes in the system. The solution may involve having long-running writes periodically wait for writeConcern if they have previously replicated writes. |