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

Disable WiredTiger cursor caching and introduce more aggressive file handle sweeps in testing

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.1, 4.3.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v4.2
    • Execution Team 2019-08-12, Execution Team 2019-08-26

      The objective is to disable WiredTiger cursor caching by setting this parameter above 0 in some builds.

      The default is -100, which enables caching in WiredTiger because it is less than or equal to 0, and also uses MongoDB cursor caching with a size of 100.

      Copied fromĀ SERVER-41494:

      Lower the following WiredTiger file_manager parameters to wiredtiger_open:

      • close_handle_minimum: number of handles open before the file manager will look for handles to close. The WT default is 250. Lower to a more reasonable number like 4.
      • close_idle_time: amount of time in seconds a file handle needs to be idle before attempting to close it. The default is 28 hours. Lower to 10 seconds.
      • close_scan_interval interval in seconds at which to check for files that are inactive and close them. The WT default is 10. Lower to 5 seconds.

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: