Add Multiplanner exit scenario counters to explain

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There are multiple reasons why the multiplanner can exit:

      • One plan hit EOF
      • Filled initial batch
      • Maximum # works hit (by default the larger of 10k or 30% of collection)
      • All plans hit memory limit and query fails

      It would be helpful to track which codepath is hit for investigations of customer issues exposed in explain. SERVER-105490 will handle this for serverStatus() and FTDC.

              Assignee:
              Unassigned
              Reporter:
              Ben Shteinfeld
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: