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

Treat maxValidateMemoryUsageMB as an absolute limit

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Storage Execution

    Description

      Right now, we allow double maxValidateMemoryUsageMB during the second phase of validation. It appears like we use double the memory limit but we actually double count the number of index keys in the first phase. We can update the comment to make this more clear. If a user sets maxValidateMemoryUsage to their max available memory like in atlas, validation can OOM because our limit calculation undercounts actual memory usage/ignores other metadata for each key. We should respect maxValidateMemoryUsageMB as the memory limit and consider doubling the server default.

      We want to consider accounting for other metadata that is stored along with each key during validation when calculating the estimated memory usage.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            shinyee.tan@mongodb.com Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: