Move memory stats from OpCtx to ClientCursor for sharded multi-batch

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • QI 2025-02-17
    • None
    • 3
    • 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().

            Assignee:
            Chris Wolff
            Reporter:
            Chris Wolff
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: