[SERVER-81780] WaitForWriteConcern should not be skipped entirely for local commands Created: 03/Oct/23 Updated: 02/Feb/24 |
|
| Status: | In Progress |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Daotang Yang |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||
| Sprint: | Execution Team 2024-02-05, Execution Team 2024-02-19 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently we have a check very early in the code to skip waiting for write concern completely if the command targets a non-replicated DB. I think this is incorrect for 2 reasons:
|