Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.4.16, 3.6.6, 4.0.0-rc0
Affects Version/s: 3.7.9
Component/s: Testing Infrastructure
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v3.6
Sprint:
TIG 2018-06-04
Linked BF Score:
0
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

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

Assignee:: Jonathan Abrahams (Inactive)
Reporter:: Robert Guo (Inactive)
Participants:: Githook User, Jonathan Abrahams, Robert Guo
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: May 17 2018 07:04:02 PM UTC
Updated:: Oct 29 2023 10:31:44 PM UTC
Resolved:: May 18 2018 07:07:12 PM UTC
Confidence Status Last Update:: 18/May/18 4:03 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates