-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines - Server Integration
-
Fully Compatible
-
v8.1, v8.0, v7.0, v6.0
-
RSS Sydney - 2024-06-25, RSS Sydney - 2024-07-09, RSS Sydney - 2024-07-23, Hoity-Toity - 2024-12-10, FarewellDaniel - 2025-02-18, HappyAddy - 2025-03-04, PastaLaVista - 2025-03-18, pro-duck-tive - 2025-04-01, meow meow meow - 2025-04-15, RSS Sydney - 2025-04-29, Bananini - 2025-05-13
-
(copied to CRM)
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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
-
- Closed
-
-
SERVER-84449 High WiredTiger session concurrency can increase replication write latency
-
- Open
-
-
-
- Backlog
-
- related to
-
-
- Blocked
-
- split to
-
-
- Closed
-