[SERVER-27684] Remove the self-imposed 2 minute limit from hang_analyzer.py Created: 13/Jan/17  Updated: 07/Sep/17  Resolved: 18/Jan/17

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

Type: Improvement Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Jonathan Abrahams
Resolution: Done Votes: 0
Labels: bkp, tig-hanganalyzer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: TIG 2017-01-02
Participants:
Linked BF Score: 0

 Description   

As part of SERVER-14181, the hang_analyzer.py script set a timer to cause itself to exit after 2 minutes. With the changes from EVG-580, this is no longer necessary because Evergreen now sets a default time limit for the "timeout" command of 15 minutes. The time limit is also configurable via a callback_timeout_secs property in the etc/evergreen.yml project configuration.

It is desirable to allow the hang_analyzer.py script to run longer than 2 minutes in order to ensure it has ample time to dump thread stacks of any MongoDB processes still running when the task times out. Note: Until SERVER-27158 is implemented, there may be many MongoDB processes still running when the task times out.



 Comments   
Comment by Githook User [ 13/Apr/17 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-27684 Remove hang_analyzer timeout

(cherry picked from commit afd3c348e1ef81dcea51221cde13976ea6271cf7)
Branch: v3.4
https://github.com/mongodb/mongo/commit/84e93628689aba8f0e20c47f7fc2254e51e10fa6

Comment by Githook User [ 18/Jan/17 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-27684 Remove hang_analyzer timeout
Branch: master
https://github.com/mongodb/mongo/commit/afd3c348e1ef81dcea51221cde13976ea6271cf7

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