[ https://issues.apache.org/jira/browse/MESOS-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14548394#comment-14548394 ]
Timothy Chen commented on MESOS-2652: ------------------------------------- Just chatted with Ian offline, in the future we should consider expressing some priority from the frameworks even using non-revocable resource can put tasks on low priority as well, that it's a nice balance since I think cutting on [non]revocable might be too limiting. > 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)