BugZero found this defect 20 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/29/2024
MongoDB Server
No affected releases provided.
No fixed releases provided.
The logic relies on checking the numBalancerRounds returned from the balancerStatus command. However, this number is just a in-memory value of the balancer task for that mongod process. This value is not shared across the replica set. For example, if a primary was running for a while, it can have the numRounds as 600, but if it fail overs to another node that is running the balancer for the first time, the counter can be reset to 1. This means that this condition to wait for balancer round to be greater than last known round number can wait for unnecessary number of rounds.