[
https://issues.apache.org/jira/browse/MESOS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139181#comment-14139181
]
Jie Yu commented on MESOS-1662:
-------------------------------
[~chi_groupon] This is fixed in 0.20.0
commit cfa168f5136f05d01ebb5ffa3a42a118db14c43e
Author: Anton Lindström <[email protected]>
Date: Sun Aug 10 16:26:46 2014 -0700
Allowed cgroups mem isolator to limit swap by setting
memory.memsw.limit_in_bytes.
Review: https://reviews.apache.org/r/24316
> Mesos doesn't limit swap
> ------------------------
>
> Key: MESOS-1662
> URL: https://issues.apache.org/jira/browse/MESOS-1662
> Project: Mesos
> Issue Type: Bug
> Components: isolation
> Affects Versions: 0.19.1
> Reporter: Andrew Forgue
> Assignee: Anton Lindström
> Fix For: 0.20.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
