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

[4.2] Calculate index build memory usage per key based on BSONObj buffer capacity, not size

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.6.0, 4.0.0, 4.2.0
    • 4.2.3
    • None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2019-12-30
    • 0

    Description

      Index builds limit their memory usage with the parameter maxIndexBuildMemoryUsageMegabytes, which defaults to 500MB. The memory usage calculation depends on the BSONObj accurately reporting its memory usuage in memUsageForSorter().

      BSONObj reports its memory usage as the size of the object, but not the capacity of the buffer holding that object. This is problematic because index builds can use significantly more memory than they they should.

      We should change the imlementation of memUsageForSorter() to report the size of the underlying SharedBuffer, in a very similar way to  what we did for in SERVER-42931.

       

       

      Attachments

        Activity

          People

            milkie@mongodb.com Eric Milkie
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: