[SERVER-66838] clearJumbo test is not waiting a full balancer round in case of stepdown Created: 27/May/22  Updated: 29/Oct/23  Resolved: 08/Jun/22

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

Type: Bug Priority: Major - P3
Reporter: Silvia Surroca Assignee: Silvia Surroca
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2022-06-13
Participants:
Linked BF Score: 25

 Description   

The test clearJumbo is failing occasionally (BF-25252) because the function waitForBalancerToRun is not waiting a full round when there is a configsvr stepdown in-between the round.

Regarding the logs, when the configsvr recovers from the stepdown, the command balancerStatus returns an incremented numBalancerRounds. Logs with filters can be found here where you can see how the _configsvrBalancerStop command is called immediately after the "CSRS balancer is starting" because of a stepdown-stepup.

A quick suggestion would be to use the balancerCollectionStatus command instead of the balancerStatus cause it returns more detailed information.



 Comments   
Comment by Githook User [ 08/Jun/22 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-66838 clearJumbo test is not waiting a full balancer round in case of stepdown
Branch: master
https://github.com/mongodb/mongo/commit/e64ccf3ea72b6a5fd560b84e39abad823e0a8319

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