[SERVER-72408] Default timeout for receiveChunkWaitForRangeDeleterTimeoutMS is too low at agg_collstats_expr.js Created: 28/Dec/22 Updated: 29/Oct/23 Resolved: 05/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0.3 |
| Fix Version/s: | 6.0.4, 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pol Pinol | Assignee: | Pol Pinol |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v6.2, v6.0
|
||||||||||||
| Sprint: | Sharding EMEA 2022-12-26 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 5 | ||||||||||||
| Description |
|
The receiveChunkWaitForRangeDeleterTimeoutMS parameter makes a recipient of a migration to wait for range deletions in intersecting chunk ranges to finish before continuing with the ongoing migration. The default timeout is currently 10 seconds, which is a number that is too low for the current test agg_collstats_expr.js. This is causing sometimes to have failures (BF-26988) on this test. I propose to increase the default value to a minute and a half (90 seconds), which is the current overall timeout for migrations. |
| Comments |
| Comment by Githook User [ 05/Jan/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: (cherry picked from commit 15e368a4c6955b91ccde175855b5bba79b609f01) |
| Comment by Githook User [ 05/Jan/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: |