[SERVER-79420] Make hang analyzer generate task to do analysis in Created: 27/Jul/23  Updated: 29/Oct/23  Resolved: 21/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Trevor Guidry Assignee: Trevor Guidry
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

Taken from scope

  • Create infrastructure for analyzing the core dumps asynchronously.
    • AMI (found from task definition)
    • Binaires download link
    • Core dump download link
    • Debug symbols download link
    • Automatically trigger from the failed evergreen tasks and gather all of the needed inputs from the original evergreen task.
    • Outputs an “Hang Analyzer Output” zip file that could be uploaded to the hung evergreen task.
    • Run analysis on the same AMI that the original process was run on.
    • Make the new hang-analyzer results as discoverable as possible to users.
  • We are heavily limited by evergreen here.
  • The appendix has the proposed plan for making the results readily available to users.
    • In the current period when the core dumps and data files are uploaded, we generate a new task that will take the inputs and run analysis.
    • Allocates matching AMIs to generate backtraces.
    • Create appropriate logging and alerting on failure.
    • It is possible we might switch to a design in the alternatives section below if we run into issues with this method.
    • Inputs:
    • Requirements:
    • Generating a new task in the 15 minute period after a task timeout.


 Comments   
Comment by Githook User [ 21/Sep/23 ]

Author:

{'name': 'Trevor Guidry', 'email': 'trevor.guidry@mongodb.com', 'username': ''}

Message: SERVER-79420 Do async core processing in generated task
Branch: master
https://github.com/mongodb/mongo/commit/d2b4f3e59180e317fac8881581d45472dbafcc8a

Generated at Thu Feb 08 06:40:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.