You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Qian Zhang (Jira)" <ji...@apache.org> on 2019/11/27 02:53:00 UTC

[jira] [Assigned] (MESOS-10033) Design per-task cgroup isolation

     [ https://issues.apache.org/jira/browse/MESOS-10033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Qian Zhang reassigned MESOS-10033:
----------------------------------

    Assignee: Andrei Budnik

> Design per-task cgroup isolation
> --------------------------------
>
>                 Key: MESOS-10033
>                 URL: https://issues.apache.org/jira/browse/MESOS-10033
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Greg Mann
>            Assignee: Andrei Budnik
>            Priority: Major
>              Labels: foundations
>
> To provide container resource isolation which more closely matches the isolation implied by the Mesos nested container API, we should limit CPU and memory on a per-task basis. The current Mesos containerizer implementation limits CPU and memory at the level of the  executor only, which means that tasks within a task group can burst above their CPU or memory resources. Instead, we should apply these limits using per-task cgroups.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)