[SERVER-78397] Set the balancerStop command to a bigger timeout than `receiveChunkWaitForRangeDeleterTimeoutMS` on tests Created: 23/Jun/23  Updated: 02/Aug/23  Resolved: 02/Aug/23

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

Type: Bug Priority: Major - P3
Reporter: Silvia Surroca Assignee: Silvia Surroca
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-76339 Increase ShardedClusterFixture's time... Closed
Related
Assigned Teams:
Sharding EMEA
Operating System: ALL
Sprint: Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07
Participants:
Linked BF Score: 5

 Description   

balancerStop command waits for the current balancer round to finish before returning a response to the user.

Since the migration timeout (receiveChunkWaitForRangeDeleterTimeoutMS, set to 90 sec) is bigger than the balancerStop maxTimeMS parameter, a balancerStop command failure would either hide a more valuable error pointing to the migration process or raise an expected error on slow variants.

The purpose of this ticket is to increase the timeout of the balancerStop called from the ShardedClusterFixture on tearDown in order to avoid hiding migration errors and improve the debugability.


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