-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
RSS Sydney
-
RSS Sydney - 2024-06-25, RSS Sydney - 2024-07-09, RSS Sydney - 2024-07-23, Hoity-Toity - 2024-12-10
-
(copied to CRM)
We maintain an unbounded cache of WiredTiger sessions. And each of these sessions has a cursor cache.
Because we asynchronously release sessions into the cache without a ticket, we can accumulate more sessions than the execution control system can limit.
The current limit is just a 5 minute idle timeout.
The size of these idle sessions can affect WiredTiger performance in some algorithms. We should impose a limit on the number of cached sessions and also expose metrics about the size of these caches.
There is some discussion here in SERVER-84449.
- is related to
-
SERVER-82688 mongod crash, bug fix when connections > wiredtiger's session_max
- Blocked
-
SERVER-84449 High WiredTiger session concurrency can increase replication write latency
- Open
-
SERVER-97007 Release WiredTiger session while waiting for writeConcern
- Backlog