[SERVER-26842] dump the go stack traces on hung tools in the hang analyzer Created: 31/Oct/16  Updated: 19/Nov/16  Resolved: 04/Nov/16

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.4.0-rc3

Type: Improvement Priority: Major - P3
Reporter: Gabriel Russell (Inactive) Assignee: Mark Benvenuto
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Platforms 2016-11-21
Participants:
Linked BF Score: 0

 Description   

After we use gdb to get the thread stack traces, we should kill -ABRT the tools processes, and finally kill -KILL the processes, in case they're hard hung.
I think we should wait a few seconds between the ABRT and the KILL to give the process a moment to finish the dump.



 Comments   
Comment by Githook User [ 04/Nov/16 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-26842 dump the go stack traces on hung tools in the hang analyzer
Branch: master
https://github.com/mongodb/mongo/commit/cc32f2cf5990bfefafaf9cab08eabe944f4ade34

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