-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently the $group tracks memory so it knows when it should spill. The memory usage tracker for this lives in GroupProcessor. We should update the group stage so that it checks a feature flag, and if it's true, updates the memory tracker with the upstream operations-scoped tracker, which will report memory for the stage into CurOp.
With this in place, we can write end-to-end JS tests that can show that profiles and slow query logs will show the metrics.
- is blocked by
-
SERVER-103337 Fix memory tracker propagation on killCursor and $exchange
-
- In Progress
-
- is depended on by
-
SERVER-101140 Add memory tracking metrics to the slow query log
-
- In Progress
-
- is related to
-
SERVER-102384 Add memory stats for $group to explain execution stats
-
- In Progress
-
- related to
-
SERVER-100793 Add memory tracking metrics to system.profile
-
- Closed
-