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

Posted to issues@mesos.apache.org by "Ian Downes (JIRA)" <ji...@apache.org> on 2015/05/29 23:36:17 UTC

[jira] [Resolved] (MESOS-2652) Update Mesos containerizer to understand revocable cpu resources

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

Ian Downes resolved MESOS-2652.
-------------------------------
    Resolution: Fixed

Branch: refs/heads/master
Commit: b8b9255ebeb1ae6ac8e854f1267c04915039f4bd
Parents: 6de149e
Author: Ian Downes <id...@twitter.com>
Authored: Fri May 15 18:03:45 2015 -0700
Committer: Ian Downes <id...@twitter.com>
Committed: Fri May 29 14:33:21 2015 -0700

> Update Mesos containerizer to understand revocable cpu resources
> ----------------------------------------------------------------
>
>                 Key: MESOS-2652
>                 URL: https://issues.apache.org/jira/browse/MESOS-2652
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Vinod Kone
>            Assignee: Ian Downes
>              Labels: twitter
>
> The CPU isolator needs to properly set limits for revocable and non-revocable containers.
> The proposed strategy is to use a two-way split of the cpu cgroup hierarchy -- normal (non-revocable) and low priority (revocable) subtrees -- and to use a biased split of CFS cpu.shares across the subtrees, e.g., a 20:1 split (TBD). Containers would be present in only one of the subtrees. CFS quotas will *not* be set on subtree roots, only cpu.shares. Each container would set CFS quota and shares as done currently.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)