Thanks, I'd normally read code to figure this kind of thing out but
C++ is one of the
few languages I have no clue with.

What I'll do then (I'm on RHEL) is install libcgroup, start cgconfig
and see what happens
with that new --isolation flag.

Part of the reason I was asking is I wasn't clear that the tasks I'm
sending out with RAM
and CPU allocations on them are actually enforced out of the box - is
that right?

We're running Marathon and shipping out jobs with 256MbRAM/01.CPU requirements,
and seems like the slaves are reporting used resources based on those numbers.

I think it's a bit unlikely these random jobs are actually using
exactly those resources,
and so I wondered if we're enforcing it anywhere.



On 9 June 2014 17:02, Jie Yu <[email protected]> wrote:
> Hi Dick,
>
>>
>> what croup isolation provides over stock posix / process isolation
>
>
> Currently, mesos provides cpu and memory isolation through cgroups on Linux
> boxes '--isolation=cgroups/cpu,cgroups/mem'
>
>> the configuration required to setup cgroups
>
>
> If no other service on the host uses cgroup (no cgroup subsystems being
> mounted), then it should be pretty simple because mesos will mount
> corresponding subsystems for you. You can choose the root hierarchy using
> the following slave flag:
>
>     add(&Flags::cgroups_hierarchy,
>         "cgroups_hierarchy",
>         "The path to the cgroups hierarchy root\n",
>         "/sys/fs/cgroup");
>
> If some services on the host are using cgroup (e.g, systemd), then it
> depends on how cgroups are mounted.
>
> - Jie
>
>
>
> On Mon, Jun 9, 2014 at 3:09 AM, Dick Davies <[email protected]> wrote:
>>
>> So we're running with default isolation (posix)
>> and thinking about enabling cgroups (mesos 0.17.0
>> right now but the upgrade to 0.18.2 was seamless
>> in dev. so that'll probably happen too).
>>
>> I just need to justify the effort and extra complexity,
>> so can someone explain briefly
>>
>> * what croup isolation provides over stock posix / process isolation
>> * the configuration required to setup cgroups
>>
>> Thanks!
>
>

Reply via email to