[SERVER-38779] Build a mechanism to periodically cleanup old WT sessions from session cache - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.6.11, 4.0.6, 4.1.7
Component/s: Storage
Labels:
- RF

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.0, v3.6
Sprint:
Storage Engines 2018-12-31, Storage Engines 2019-01-14, Storage Engines 2019-01-28
Case:
Story Points:
8

Description

The way session cache is maintained, idle sessions keep accumulating in the session cache. If the workload doesn't use all the idle sessions, the oldest sessions stay open forever. In some cases these sessions might hold some resources inside WiredTiger, which can cause problems. eg: dhandles that never close in WiredTiger.

This ticket is to build a mechanism around the session cache, to cleanup old sessions that have been idle for too long.

Attachments

Issue Links

is related to

WT-4336 With MongoDB, sweep attempts after table drops do not always close active dhandles

Closed

WT-4513 Investigate improvements in session's dhandle cache cleanup

Closed

related to

SERVER-39355 Collection drops can block the server for long periods

Closed

Activity

People

Assignee:: Sulabh Mahajan

Reporter:: Sulabh Mahajan

Participants:: Bruce Lucas, Githook User, Jackie Chu, Sulabh Mahajan

Votes:: 4 Vote for this issue

Watchers:: 16 Start watching this issue

Dates

Created:: Dec 27 2018 03:06:14 AM UTC

Updated:: Dec 02 2022 07:17:08 PM UTC

Resolved:: Jan 16 2019 12:26:15 AM UTC