[SERVER-84356] Make Sharding and User Command Write Concern Timeouts Configurable via Server Parameter Created: 20/Dec/23 Updated: 05/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Brett Nawrocki | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cs-neweng, cs-techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||
| Participants: | |||||||||
| Description |
|
We currently hardcode these two (kWriteConcernTimeoutSharding{60} and kWriteConcernTimeoutUserCommand{60} ) values at 60 seconds each. In some cases, it might be desirable to modify these values, so they should be configurable via a server parameter instead. |