[SERVER-39324] Profiler entries may omit execStats metrics Created: 31/Jan/19  Updated: 06/Dec/22

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

Type: Bug Priority: Major - P3
Reporter: Bernard Gorman Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 1
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Assigned Teams:
Query Execution
Operating System: ALL
Participants:
Case:

 Description   

Towards the end of find command execution, we call endQueryOp to fill out some CurOp metrics. Among these is OpDebug::execStats, which we populate only after checking that the operation is eligible for profiling.

However, the CurOp timer continues to tick after this point. If the operation's duration is below the slowMS threshold when we check profiling eligibility in endQueryOp but has exceeded slowMS by the time we check again at the very end of the command code path, then we will incorrectly profile the operation without execStats.


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