[ https://issues.apache.org/jira/browse/MESOS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085098#comment-14085098 ]
Anton Lindström edited comment on MESOS-1662 at 8/4/14 7:01 PM: ---------------------------------------------------------------- I'm changing from memory.limit_in_bytes to memory.memsw.limit_in_bytes where it's added. Review at https://reviews.apache.org/r/24246/ was (Author: antonl): I'm changing from memory.limit_in_bytes to memory.memsw.limit_in_bytes where it's added. Sending a review right away. > 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 > > 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.2#6252)