[SERVER-18286] Adjust the value of the WiredTiger file_manager values passed to wiredtiger_open Created: 30/Apr/15  Updated: 19/Sep/15  Resolved: 13/May/15

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: None
Fix Version/s: 3.0.4, 3.1.3

Type: Improvement Priority: Major - P3
Reporter: Daniel Pasette (Inactive) Assignee: Daniel Pasette (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on WT-1929 LSM and YCSB 50/50 - Is it scale up t... Closed
Related
related to WT-1930 Change meaning of file_manager.close_... Closed
is related to SERVER-17907 B-tree eviction blocks access to coll... Closed
Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: Quint Iteration 3
Participants:

 Description   

The WiredTiger engine automatically closes and evicts idle tables in order to free cache space quickly. There are three knobs that can be adjusted to tune when and how often the file manager checks for idle tables.

  • close_handle_minimum: number of handles open before the file manager will look for handles to close; default 250
  • close_idle_time: amount of time in seconds a file handle needs to be idle before attempting to close it; default 30 secs
  • close_scan_interval : interval in seconds at which to check for files that are inactive and close them; default 10 secs

The defaults should be increased in the MongoDB integration layer. This will result in the regular LRU eviction policy to control when collections are evicted from cache and is more in line with behavior most users expect.



 Comments   
Comment by Daniel Pasette (Inactive) [ 13/May/15 ]

Will re-address fix if WT-1930 is resolved

Comment by Githook User [ 13/May/15 ]

Author:

{u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}

Message: SERVER-18286 Increase the value of the WiredTiger close_idle_time

Set the value of close_idle_time to ~28 hours to prevent idle
collections and indexes from being forced out of cache
Branch: v3.0
https://github.com/mongodb/mongo/commit/564140a0aae77d6c5a959e7a2656f2fc32047930

Comment by Githook User [ 13/May/15 ]

Author:

{u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}

Message: SERVER-18286 Increase the value of the WiredTiger close_idle_time

Set the value of close_idle_time to ~28 hours to prevent idle
collections and indexes from being forced out of cache
Branch: master
https://github.com/mongodb/mongo/commit/f5450e9bc5cf63c3dc4d9cb416713b0f6970e6d4

Comment by Daniel Pasette (Inactive) [ 12/May/15 ]

cc: michael.cahill
Adding a temporary fix to be backported to 3.0, but won't close this ticket.
Waiting on API change from WT API which will make setting close_handle_minimum=0 turns off sweep of handles, but won't negatively impact LSM which should continue to close obsolete trees.

Generated at Thu Feb 08 03:47:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.