[SERVER-84443] Bring back no timeout write concern for commands in resharding coordinator Created: 28/Dec/23 Updated: 08/Jan/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.1.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cs-80-required, cs-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Story Points: | 2 | ||||||||||||||||
| Description |
|
A refactor made the coordinator use the appendMajorityWriteConcern helper method to attach the write concern of some of the commands it sends to the participants. However, it also inadvertently changed some of the commands that originally had no timeout to something with one. This is because it changed some of the places where it originally used this constant to call appendMajorityWriteConcern, which uses a different constant with non-zero wtimeout value. |