You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Arunabha Ghosh <ar...@gmail.com> on 2015/05/02 04:49:27 UTC
Problem using cgroups/mem isolator
Hi,
I'm trying to use the cgroups memory isolator, but after setting
--isolation to 'cgroups/cpu,cgroups/mem' I'm getting the following error in
the logs
mesos-slave[12416]: Failed to create a containerizer: Could not create
MesosContainerizer: Could not create isolator cgroups/mem:
'memory.memsw.limit_in_bytes' is not available
The cgroups cpu isolator seems to be working as setting --isolation to
'cgroups/cpu.posix/mem' works fine.
Has anyone run into this before ? Any help debugging this is greatly
appreciated.
Thanks,
Arunabha
Re: Problem using cgroups/mem isolator
Posted by Ian Downes <id...@twitter.com>.
The link from Tim suggests that not all kernels enable this. Could you
please file a bug report and we'll improve the handling of this in Mesos.
ian
On Sat, May 2, 2015 at 2:20 PM, CCAAT <cc...@tampabay.rr.com> wrote:
> On 05/02/2015 02:17 PM, Tim Chen wrote:
>
>> Hi Arunabha,
>>
>> Which linux distro/version are you using?
>>
>> A quick search on google finds some settings that might be required to
>> turn on memsw.limit_in_bytes options for cgroups:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348688
>>
>> Tim
>>
>
> Maybe the mesos code(s) needs to perform a kernel test to see what is
> enabled and what is not available, regardless of distro? Or does it make
> more sense to have functions based on cgroups, whether or not they are
> properly activated in the kernel?
>
>
> James
>
>
>
>
Re: Problem using cgroups/mem isolator
Posted by CCAAT <cc...@tampabay.rr.com>.
On 05/02/2015 02:17 PM, Tim Chen wrote:
> Hi Arunabha,
>
> Which linux distro/version are you using?
>
> A quick search on google finds some settings that might be required to
> turn on memsw.limit_in_bytes options for cgroups:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348688
>
> Tim
Maybe the mesos code(s) needs to perform a kernel test to see what is
enabled and what is not available, regardless of distro? Or does it make
more sense to have functions based on cgroups, whether or not they are
properly activated in the kernel?
James
Re: Problem using cgroups/mem isolator
Posted by Tim Chen <ti...@mesosphere.io>.
Hi Arunabha,
Which linux distro/version are you using?
A quick search on google finds some settings that might be required to turn
on memsw.limit_in_bytes options for cgroups:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348688
Tim
On Fri, May 1, 2015 at 7:49 PM, Arunabha Ghosh <ar...@gmail.com>
wrote:
> Hi,
> I'm trying to use the cgroups memory isolator, but after setting
> --isolation to 'cgroups/cpu,cgroups/mem' I'm getting the following error in
> the logs
>
> mesos-slave[12416]: Failed to create a containerizer: Could not create
> MesosContainerizer: Could not create isolator cgroups/mem:
> 'memory.memsw.limit_in_bytes' is not available
>
> The cgroups cpu isolator seems to be working as setting --isolation to
> 'cgroups/cpu.posix/mem' works fine.
>
> Has anyone run into this before ? Any help debugging this is greatly
> appreciated.
>
> Thanks,
>
> Arunabha
>
Re: Problem using cgroups/mem isolator
Posted by Dario Rexin <da...@mesosphere.io>.
Hi Arunabha,
you may need to enable memory isolation in the kernel. You can do that by adding cgroup_enable=memory to your kernel boot options.
Cheers,
Dario
> On 02.05.2015, at 04:49, Arunabha Ghosh <ar...@gmail.com> wrote:
>
> Hi,
> I'm trying to use the cgroups memory isolator, but after setting --isolation to 'cgroups/cpu,cgroups/mem' I'm getting the following error in the logs
>
> mesos-slave[12416]: Failed to create a containerizer: Could not create MesosContainerizer: Could not create isolator cgroups/mem: 'memory.memsw.limit_in_bytes' is not available
>
> The cgroups cpu isolator seems to be working as setting --isolation to 'cgroups/cpu.posix/mem' works fine.
>
> Has anyone run into this before ? Any help debugging this is greatly appreciated.
>
> Thanks,
>
> Arunabha