[SERVER-53456] Hang analyzer creates multiple invocations Created: 18/Dec/20  Updated: 29/Oct/23  Resolved: 26/Feb/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Bug Priority: Major - P3
Reporter: Raiden Worley (Inactive) Assignee: Siran Wang (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng, tig-hanganalyzer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: STM 2021-03-08
Participants:
Story Points: 1

 Description   

Running the hang analyzer with no processes specified causes it to discover resmoke and send it a SIGUSR1 to dump info. When Resmoke receives a SIGUSR1 it invokes the hang analyzer targeting its subprocesses. Now there are two hang analyzers that will target the same mongo and mongods, creating attachment failures, overwriting output files, and sometimes hanging as well.

This doesn't happen in CI because we only target python processes, but it's intended that a local invocation without specifying processes should work.



 Comments   
Comment by Githook User [ 26/Feb/21 ]

Author:

{'name': 'Siran Wang', 'email': 'siran.wang@mongodb.com', 'username': 'vincivans'}

Message: SERVER-53456 let hang_analyzer target only c++ process
Branch: master
https://github.com/mongodb/mongo/commit/f589354f0fe82b2fd489ea13e76acd163120aeb6

Comment by Robert Guo (Inactive) [ 21/Dec/20 ]

A couple of options.

1. have the hang analyzer just target c++ processes by default
2. Have a global hang analyzer lock file to allow only a single instance to run.

We can try option 1 first since the majority of users on Server will care about C++ processes only.

Generated at Thu Feb 08 05:30:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.