[SERVER-83139] Increase reshardingCriticalSectionTimeoutMillis for ShardingTest fixture Created: 10/Nov/23  Updated: 27/Jan/24  Resolved: 27/Jan/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 8.0.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Abdul Qadeer Assignee: Kruti Shah
Resolution: Fixed Votes: 0
Labels: cs-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Cluster Scalability
Backwards Compatibility: Fully Compatible
Sprint: Cluster Scalability 2023-12-25, Cluster Scalability 2024-1-8, Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5
Participants:
Linked BF Score: 5
Story Points: 1

 Description   

We have seen a lot of BFs arising from reshardingCriticalSectionTimeoutMillis timing out in test infra due to slower machines. A few examples include BF-30637, BF-30377, and BF-30354. To avoid more such coming up due to users issuing reshardCollection via ShardingTest fixture instead of ReshardingTest fixture, we should increase the default timeout internally inside ShardingTest fixture, while allowing any explicit override.



 Comments   
Comment by Githook User [ 26/Jan/24 ]

Author:

{'name': 'Kruti Shah', 'email': '70412403+krutishah139@users.noreply.github.com', 'username': 'krutishah139'}

Message: SERVER-83139 Increase reshardingCriticalSectionTimeoutMillis server parameter (#17748)

GitOrigin-RevId: fda3f0d321fa1565237696895d8d513e011e7dd5
Branch: master
https://github.com/mongodb/mongo/commit/af07816d6681955a0bb1a212bad6b3ebb503c171

Generated at Thu Feb 08 06:51:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.