Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-99737

Populate sort stats about memory and spilling in allPlansExecution explain rejectedPlans

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We don't collect the stats from the sorter until consuming all results from the input stage. The rejected plans will show 0 spills, mem usage, etc if the input stage is not fully consumed during multiplanning. This may lead to a misleading assumption that no spilling has occurred during multiplanning.

            Assignee:
            Unassigned Unassigned
            Reporter:
            jess.balint@mongodb.com Jess Balint
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: