-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.0.0-rc10
-
Component/s: WiredTiger
-
Fully Compatible
-
ALL
-
Quint Iteration 3.1.2, Quint Iteration 3, Quint Iteration 5
ISSUE SUMMARY
WiredTiger allows MongoDB to open an unbounded number of WiredTiger sessions, which means that despite a limited number of WiredTiger cursors per session, the total number of cached sessions an cursors may lead to excessive memory use.
USER IMPACT
MongoDB with WiredTiger may consume too much memory in some situations, leading to excessive memory use beyond the normal WiredTiger database cache, potentially triggering out of memory conditions and even the OOM killer.
WORKAROUNDS
None.
AFFECTED VERSIONS
MongoDB 3.0.0 through 3.0.4.
FIX VERSION
The fix is included in the 3.0.5 production release.
Original description
Running RC10 with the c# driver, 50 threads concurrently bulk inserting/updating/reading, I see stacktraces in the console output followed by a big speed drop. The speed drop appears to be related to reads, but I can't be sure yet.
I will attempt to reproduce this with a long running test and report back.
- is duplicated by
-
SERVER-17456 Mongodb 3.0 wiredTiger storage engine memory usage too high.
- Closed
-
SERVER-18821 64 sessions created in single threaded workload
- Closed
-
SERVER-19273 Short range scan using YCSB cause mongodb crash
- Closed
-
SERVER-19562 Restore error: insertion error with out-of-memory condition
- Closed
- is related to
-
NODE-487 WiredTiger memory leak
- Closed
-
SERVER-17424 WiredTiger uses substantially more memory than accounted for by cache
- Closed
- related to
-
SERVER-17364 Idle cursors shouldn't hold storage engine resources
- Closed