Add conditional operation-wide memory tracking to GroupProcessorBase

XMLWordPrintableJSON

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

            Assignee:
            Erin Liang
            Reporter:
            Chris Wolff
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: