[
https://issues.apache.org/jira/browse/MESOS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085145#comment-14085145
]
Ian Downes commented on MESOS-1662:
-----------------------------------
I tend to agree that Mesos should be able to limit memory+swap but this change
needs some consideration because users may be running jobs that do use swap and
which would now OOM unexpectedly.
I can imagine users limiting memory and swap independently so perhaps this
needs some discussion?
> 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)
