-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 2.8.0-rc2
-
Component/s: Storage
-
Minor Change
-
Linux
-
v4.0, v3.6
-
(copied to CRM)
The memory size is taken into account within various components today:
- We set the default WiredTiger cache_size to approximately 1/2 of the memory size
- When ephemeral storage is in use we consider the memory limit in place to determine the default oplog size
- We set the tcmalloc cache size to 1/8th of the available memory
In all of these cases we should take the actual memory constraint that we're operating under into account rather than the total system memory – for example when running MongoDB within containers.
- is depended on by
-
SERVER-39966 Report both total actual system memory and cgroup memory limit in hostInfo
-
- Closed
-
- is related to
-
-
- Closed
-
-
SERVER-52596 Detect memLimitMB in K8S pod and inform WiredTigerCacheSize calculation for pod RAM instead of total system RAM
-
- Closed
-