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

Cap $in length in plan cache key with internalQueryMaxScansToExplode + 1

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.2.1, 7.3.0-rc0, 7.0.5
    • None
    • None
    • None
    • Fully Compatible
    • v7.2, v7.0
    • QE 2023-12-11
    • 35

    Description

      The reason we add $in length to plan cache key is possible explodeForSort optimization.

      We have internalQueryMaxScansToExplode query knob that limits the maximum number of explode for sort index scans. 

      We can use it to limit the number of plan cache entries.

      Attachments

        Activity

          People

            ivan.fefer@mongodb.com Ivan Fefer
            ivan.fefer@mongodb.com Ivan Fefer
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: