-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Storage, WiredTiger
-
None
-
Fully Compatible
-
Windows
-
-
Platform C (11/20/15)
When deploying MongoDb with WT on Windows OSs, physical memory is exhausted by file system caching, irrespective of WiredTigerCacheSizeGB. This makes it impossible to limit the amount of physical memory used by MongoDb, which means it cannot be deployed alongside other processes on the same physical hardware.
The file system cache dedicated to WT I/O does not appear to be released under memory stress, and other processes may be starved for memory.
Once the file system cache has consumed the majority of physical memory, idling MongoDb has no effect on releasing file system memory. The only way to reclaim the file system memory is to restart MongoDb.
This effectively makes MongoDb with WT unusable as an embedded database - an area I think that MongoDb (the company) underestimates.
- depends on
-
WT-2200 Change WiredTiger caching strategy on Windows
- Closed
-
SERVER-21349 WiredTiger changes for 3.2.0-rc3
- Closed
- is related to
-
SERVER-19795 mongod memory consumption higher than WT cache size (at least on Windows 2008 R2)
- Closed
-
WT-1990 Prevent Windows from mapping.wt files
- Closed
- related to
-
SERVER-29465 Add warning about Windows SystemFileCacheSize for WiredTiger
- Closed