Exchange memory tracking should always only report to curOp of consumer0

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After SERVER-124190, The memory tracker for exchange can report to a curOp for a non-zero consumer if the memory tracking stage was lazily created. We could get around this by eagerly creating a memory tracker in exchange if none exists already. See https://github.com/10gen/mongo/pull/59356/changes#r3668932941 for more context. 

            Assignee:
            Unassigned
            Reporter:
            Erin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: