Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-1856

Don't close handles until a threshold of in-use handles has been reached

    Details

    • Type: Task
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT2.6.0
    • Labels:

      Description

      At the moment WiredTiger has a sweep server that automatically closes file handles if they have been idle for over 30 seconds. Idle means that there are no cursors open on the file.

      That can lead to undesirable behavior - we may flush a file from cache, even when the cache isn't full.

      It makes sense to only consider closing handles once we are using a certain number of file handles. A reasonable start might be 200 file handles.

      This is related to MongoDB SERVER-17907

        Issue Links

          Activity

          Hide
          monkey101 Dan Pasette (Inactive) added a comment -

          This issue is reflected in mongodb jira as https://jira.mongodb.org/browse/SERVER-17514

          Show
          monkey101 Dan Pasette (Inactive) added a comment - This issue is reflected in mongodb jira as https://jira.mongodb.org/browse/SERVER-17514
          Hide
          keith.bostic Keith Bostic added a comment -

          Closed with the merge of WT-1858, note in SERVER-17514.

          Show
          keith.bostic Keith Bostic added a comment - Closed with the merge of WT-1858 , note in SERVER-17514 .
          Hide
          ramon.fernandez Ramon Fernandez added a comment -

          Additional ticket information from GitHub

          This ticket was referenced in the following commits:
          Show
          ramon.fernandez Ramon Fernandez added a comment - Additional ticket information from GitHub This ticket was referenced in the following commits: 709cc8d7ac85d31aeae2387b192092910e6cf854

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 48 weeks, 6 days ago
                Date of 1st Reply: