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

Ignore wiredTiger cacheSizeGB > RAM

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: WiredTiger
    • None
    • Storage Execution

      In SERVER-20056 we warn if the cache size is greater than 80% of RAM. I've seen a case where the cacheSizeGB was accidentally set to 3x RAM and this led to some weird results including OOMKiller.

      Perhaps as well as the startup warning, we could ignore (or correct) any cacheSizeGB greater than RAM to save admin's from destabilizing a node? 

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            nicholas.cottrell@mongodb.com Nic Cottrell
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: