[SERVER-27158] Shut down clusters on finished jobs in resmoke Created: 22/Nov/16  Updated: 07/Sep/17  Resolved: 22/Feb/17

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.4.5, 3.5.4

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Robert Guo (Inactive)
Resolution: Done Votes: 1
Labels: bkp, tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: TIG 2017-02-13, TIG 2017-03-06
Participants:
Linked BF Score: 0

 Description   

Resmoke passthroughs start up a cluster for each job. These clusters are not shut down until the entire task finishes. This makes it difficult to figure out which test did not finish in a timed out task and also adds a lot of unnecessary and sometimes misleading log messages to the end of jobs that finish early. When a job is no longer being given tests to run, it should shut down its cluster.



 Comments   
Comment by Githook User [ 26/May/17 ]

Author:

{u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robert.guo@10gen.com'}

Message: SERVER-27158 shutdown fixtures when a job finishes
Branch: v3.4
https://github.com/mongodb/mongo/commit/616f7096642d6a30ca9d38b61adbe047cbfe07cc

Comment by Githook User [ 23/Feb/17 ]

Author:

{u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robert.guo@10gen.com'}

Message: SERVER-27158 teardown_flag does not exist except for the final iteration
Branch: master
https://github.com/mongodb/mongo/commit/6ec5d44bc37e25498e79890bbc2b8fd15c6e59a4

Comment by Githook User [ 22/Feb/17 ]

Author:

{u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robert.guo@10gen.com'}

Message: SERVER-27158 shutdown fixtures when a job finishes
Branch: master
https://github.com/mongodb/mongo/commit/18be5b3302fd7f8912b5906db88637317a90d2f0

Comment by Robert Guo (Inactive) [ 22/Nov/16 ]

Doing this will allow us to make better use of the coredumps generated by the hang analyzer.

Currently the hang analyzer will generate coredumps for processes until they exceed some threshold (10GB ATM). Since each dump is typically 1GB and suites often run dozens of mongo processes, there is a high probability that we won't have the dump of the hanging node.

Generated at Thu Feb 08 04:14:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.