[SERVER-17514] Don't close handles until a threshold of in-use handles has been reached Created: 09/Mar/15 Updated: 07/Dec/16 Resolved: 10/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage, WiredTiger |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | 3.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Keith Bostic (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
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. See: https://github.com/wiredtiger/wiredtiger/issues/1856 Original Description After loading data and some short time of non-activity, all cache seems to be evicted and resident memory goes to near 0. Haven't been able to reproduce on Linux or seen it on other Windows platforms (don't have Windows 7 to test with). From the google groups thread:
|