Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.19.1
-
None
Description
When using control groups, mesos will limit memory usage, but if the CONFIG_MEMCG_SWAP config option is enabled swap usage is not limited.
This means that if a task that asked for 1G and allocated 4G, it will fill 3G of swap. The expected behavior is that the cgroup should have OOMed. The control group key for limiting both Memory+Swap is memory.memsw.limit_in_bytes (not memory.limit_in_bytes). It looks like CONFIG_MEMCG_SWAP showed up in Kernel 3.6.
Mesos should limit swap+memory if possible. I can't imagine when you'd want to limit memory but not swap, but there may be some situations.