[SERVER-59652] Allow receiveChunkWaitForRangeDeleterTimeoutMS to be set at runtime Created: 27/Aug/21 Updated: 31/Aug/21 Resolved: 31/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Sharding EMEA 2021-09-06 |
| Participants: |
| Description |
|
receiveChunkWaitForRangeDeleterTimeoutMS can only be set when starting the binary, we should allow to set the timeout at runtime, otherwise, workload tests won't be able to set it before running, which would lead to failed migrations. |
| Comments |
| Comment by Marcos José Grillo Ramirez [ 31/Aug/21 ] |
|
The receiveChunkWaitForRangeDeleterTimeoutMS parameter can already be set at runtime, this will work as long as we have a direct connection to the mongod binaries. |