-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
QI 2025-02-17
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Similar to how we did for SERVER-100762, we should transfer the OperationMemoryUsageTracker to the ClientCursor when a sharded query produces more than a single batch, and write a test that shows this works.
Do this for aggregate() to start, we may need to add more tickets for find(), distinct().
- related to
-
SERVER-100762 Stash and unstash memory metrics for aggregate() and getMore()
-
- Closed
-