[SERVER-83095] Allow callstack generator to print in-flight operations Created: 10/Nov/23  Updated: 02/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Chi-I Huang Assignee: Chi-I Huang
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Sprint: QO 2024-02-05, QO 2024-02-19
Participants:

 Description   

Logging information helps us to find the root cause queries to confirm and reproduce an underlying bug. In an incident like SERVER-83091 where there's a thread causing the mongod to hang indefinitely, we would like to know the shape of the underlying query causing the issue and how to reproduce that consistently within a short time.

Currently, we have logging for slow queries and printAllThreadStacks for this purpose. However, the former one only prints upon the completion of a query, while the latter prints the stack trace with limited information about the query shapes.

This ticket proposes to log the in-progress queries whenever printAllThreadStacks is called such that we are able to see the underlying queries contributing the those stack traces.


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