[SERVER-50213] Add "GDB" to list of processes to kill in post task Created: 10/Aug/20  Updated: 06/Dec/22  Resolved: 11/Aug/20

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

Type: Task Priority: Major - P3
Reporter: Vlad Rachev (Inactive) Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

Add "GDB" to this list



 Comments   
Comment by Vlad Rachev (Inactive) [ 11/Aug/20 ]

My understanding was wrong. I see that the evergreen agent would indeed kill GDB if it was still running. I'm still unclear as to why there is a 'kill processes' section at all, if the evergreen agent is cleaning up all of the processes it spawns, but I agree that adding 'gdb' to the list won't affect the OOM kills we are seeing.

Comment by Vlad Rachev (Inactive) [ 11/Aug/20 ]

The evergreen agent only kills shell processes it spawned, so GDB could be still be running during post-task phases. We were looking into an evergreen slowdown caused by the evergreen agent being OOM killed while running "archive.targz_pack" during "save mongo coredumps", and want to make sure GDB is not potentially running during the post-task and using up memory.

Comment by Max Hirschhorn [ 10/Aug/20 ]

The Evergreen agent does its own process cleanup before the post phase runs. What is the thinking behind adding gdb to the process_kill_list?

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