[SERVER-71143] Rewrite planning time metric to be stored/maintained by CurOp/OpDebug Created: 07/Nov/22  Updated: 29/Oct/23  Resolved: 17/Jan/23

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

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

Issue Links:
Related
related to SERVER-70646 Compute and add query planning time t... Closed
is related to SERVER-71484 Don't store queries directly on the O... Closed
Backwards Compatibility: Fully Compatible
Sprint: QO 2023-01-23
Participants:

 Description   

As it is currently implemented, the metric is maintained by PlanExplainer. This doesn't make a lot of sense as PlanExplainer is an API for writing plan summary stats and not storing execution results. 



 Comments   
Comment by Maddie Zechar [ 17/Jan/23 ]

I put this down as not needing a backport, bc it doesn't in the context of telemetry. Then I remembered that this is also being used by the system profiler. Should I backport this? cc charlie.swanson@mongodb.com james.wahlin@mongodb.com 

Comment by Githook User [ 13/Jan/23 ]

Author:

{'name': 'Maddie Zechar', 'email': 'mez2113@columbia.edu', 'username': 'madelinezec'}

Message: SERVER-71143: rewrite planning time metric to be maintained/stored by CurOp/OpDebug
Branch: master
https://github.com/mongodb/mongo/commit/4a97c2be5fb3dd35290f9924bbd662212b00737b

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