mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Downes (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MESOS-2652) Update Mesos containerizer to understand revocable cpu resources
Date Wed, 06 May 2015 17:35:00 GMT

    [ https://issues.apache.org/jira/browse/MESOS-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14530993#comment-14530993
] 

Ian Downes edited comment on MESOS-2652 at 5/6/15 5:34 PM:
-----------------------------------------------------------

IIUC that would require constantly updating cpu.shares values across all containers anytime
a container changed/was added/removed to ensure the relative weights were preserved unless
you have very extreme values. I recall Ben relating that [~kozyraki] had observed strange
behavior with CFS with very small values?

The two way split means the aggregate of the non-revocable containers dominates the revocable;
then, within each subtree, there's a weighting (proportional to the cpu) between containers
of the same type.

We should investigate both options and determine how each behaves. Created MESOS-2702.


was (Author: idownes):
IIUC that would require constantly updating cpu.shares values across all containers anytime
a container changed/was added/removed to ensure the relative weights were preserved unless
you have very extreme values. I recall Ben relating that [~kozyraki] had observed strange
behavior with CFS with very small values?

The two way split means the aggregate of the non-revocable containers dominates the revocable;
then, within each subtree, there's a weighting (proportional to the cpu) between containers
of the same type.

We should investigate both options and determine how each behaves.

> 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
>
> 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)

Mime
View raw message