Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
3.7.9
-
None
-
Fully Compatible
-
ALL
-
v3.6
-
TIG 2018-06-04
-
0
Description
This has always been an issue but we seemingly have never inserted enough data to keep the balancer busy until the nodes shut down. Now with SERVER-34555 doing heavier workloads on resmoke clusters, we've started to run into this problem.
We should have ShardedClusterFixture stop the balancer as part of its teardown process.
Attachments
Issue Links
- causes
-
SERVER-36449 ShardedClusterFixture tries to access never started mongos
-
- Backlog
-
- is depended on by
-
SERVER-34555 Migrate concurrency_sharded_with_stepdowns{,_and_balancer}.yml test suites to run directly via resmoke.py
-
- Closed
-