[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: |
|
||||||||||||
| 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: |