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

Expose an absolute dirty size to the eviction configuration parameters

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.1.0-rc0
    • WiredTiger
    • Fully Compatible
    • v4.4, v4.2, v4.0, v3.6
    • Storage Engines 2019-01-28, Execution Team 2020-05-04, Execution Team 2020-05-18, Execution Team 2020-06-01, Execution Team 2021-09-06, Execution Team 2021-09-20

    Description

      Expose two configurable options that control the targeted and maximum levels of dirty data allowed in cache. The options will accept a floating-point value in gigabytes, like cacheSizeGB.

      eviction_dirty_target can be thought of as the targeted amount of dirty data allowed in cache. Anything larger, and worker threads start eviction.
      eviction_dirty_trigger can be thought of as a maximum amount of dirty data allowed in cache before application threads start eviction.

      Attachments

        Issue Links

          Activity

            People

              josef.ahmad@mongodb.com Josef Ahmad
              dmitry.agranat@mongodb.com Dmitry Agranat
              Votes:
              3 Vote for this issue
              Watchers:
              24 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: