In DOCS-1555 we changed our recommendations for users starting the balancer from using sh.startBalancer() to sh.setBalancerState(true) because the former waits for a mongos to take the balancer lock after enabling the balancer. If we're not recommending that people use sh.startBalancer() because of this behavior, we should probably just remove that behavior so that sh.startBalancer does what we want it to.
- is related to
-
DOCS-6721 Recommend sh.startBalancer() over sh.setBalancerState(true) for re-enabling balancing
- Closed
-
SERVER-22463 sh.startBalancer should be smarter about balancing windows
- Closed
- related to
-
SERVER-19467 Race in sh.startBalancer()
- Closed
-
DOCS-1555 sh.startBalancer() might be the wrong thing for turning balancing on after turning it off
- Closed