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

Multi updates should limit memory usage to track updated RecordIds

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Execution

    Description

      We currently keep track of the updated RecordIds in a hashmap. This could end up using huge amounts of memory if a multi:true update is modifying large number of documents. The is more problematic for clustered collections, given the size of the RecordIds for clustered collections can be much larger than a regular collection. We should spill to disk instead if the memory usage crosses certain threshold.

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            arun.banala@mongodb.com Arun Banala
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: