[jira] [Updated] (MESOS-1662) Mesos doesn't limit swap
[ https://issues.apache.org/jira/browse/MESOS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-1662: -- Fix Version/s: 0.20.0 > 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)
[jira] [Updated] (MESOS-1662) Mesos doesn't limit swap
[ https://issues.apache.org/jira/browse/MESOS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1662: - Shepherd: Jie Yu > 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)
[jira] [Updated] (MESOS-1662) Mesos doesn't limit swap
[ https://issues.apache.org/jira/browse/MESOS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Forgue updated MESOS-1662: - 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. was: 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 will fill 3G of swap, whereas the cgroup should have OOMed. The proper control group key is memory.memsw.limit_in_bytes instead of memory.limit_in_bytes. (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. > 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 > > 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)
