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

Avoid scanning entire routing table during $merge stage planning

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • 4.2.24, 4.4.24, 6.0.10, 5.0.21, 7.1.0-rc2
    • None
    • None
    • Query Optimization
    • ALL

    Description

      In SERVER-35905 we added a logic to partition a $merge stage on the shards.
      This logic requires scanning the entire routing table for the collection that before 7.0+ could potentially contain millions of entry.
      For collections of large number of chunks, this logic could take seconds to be executed.
      Additionally, this logic is creating a vector of the size of the routing table, potentially consuming several GBs of RAM.

      Attachments

        Activity

          People

            backlog-query-optimization Backlog - Query Optimization
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated: