[SERVER-57507] Change maxTimeMS in collMod command in resharding_disallow_writes test Created: 07/Jun/21 Updated: 29/Oct/23 Resolved: 10/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc2, 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Luis Osta (Inactive) | Assignee: | Luis Osta (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Sprint: | Sharding 2021-06-14 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 47 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
In the postCheckConsistencyFn passed down to 'withReshardingInBackground' in `reshardind_disallow_writes.js` test, the collMod command gets called with a maxTimeMS of 5000. This is an issue in slower variants as some are configured with a low executor pool size. Hence there's no assurance that the command will be addressed in 5000 ms.
The simplest solution would either be to remove the maxTimeMS (which uses the default) or extend it to a larger number like 30,000 MS. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 10/Jun/21 ] |
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: |
| Comment by Githook User [ 10/Jun/21 ] |
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: |
| Comment by Max Hirschhorn [ 07/Jun/21 ] |
I think the maxTimeMS can be removed altogether from the test for the commands which are expected to fail with a ReshardCollectionInProgress error response. Omitting maxTimeMS from the command means the collMod command will be allowed to execute until it reaches the uassert() which throws ReshardCollectionInProgress. |