[SERVER-42045] Consider adding PID into the log message emitted by processes started by the shell Created: 02/Jul/19  Updated: 06/Dec/22  Resolved: 28/Jan/22

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

Type: Improvement Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: tig-mongorunner
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-50085 Make it easier to correlate mongo pro... Closed
Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

Right now, we only log the port of the mongo processes started up the mongo shell. When debugging hang analyzer stack traces or coredumps, it can often be helpful to know the PID of the process as well. We could change the logic to include the PID of the process as well e.g.

[js_test:transactions_on_secondaries_not_allowed] 2019-07-02T12:32:30.696-0400 d20021|6045|2019-07-02T12:32:30.696-0400 D2 COMMAND  [conn1] command: replSetGetStatus



 Comments   
Comment by Brooke Miller [ 28/Jan/22 ]

We added a PID to port map at the beginning of every test to make this correlation easier.

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