mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-2652) Update Mesos containerizer to understand revocable cpu resources
Date Tue, 14 Jul 2015 22:31:04 GMT

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

Jie Yu commented on MESOS-2652:
-------------------------------

Absolutely! I think a smart QoS controller will help as well. For instance, a OoS controller
can monitor the application specific SLA or some general indicators like CPI to predict potential
interferences and kill revocable tasks if needed.

> 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
>             Fix For: 0.23.0
>
>         Attachments: Abnormal performance with 3 additional revocable tasks (1).png,
Abnormal performance with 3 additional revocable tasks (2).png, Abnormal performance with
3 additional revocable tasks (3).png, Abnormal performance with 3 additional revocable tasks
(4).png, Abnormal performance with 3 additional revocable tasks (5).png, Abnormal performance
with 3 additional revocable tasks (6).png, Abnormal performance with 3 additional revocable
tasks (7).png, Performance improvement after reducing cpu.share to 2 for revocable tasks (1).png,
Performance improvement after reducing cpu.share to 2 for revocable tasks (10).png, Performance
improvement after reducing cpu.share to 2 for revocable tasks (2).png, Performance improvement
after reducing cpu.share to 2 for revocable tasks (3).png, Performance improvement after reducing
cpu.share to 2 for revocable tasks (4).png, Performance improvement after reducing cpu.share
to 2 for revocable tasks (5).png, Performance improvement after reducing cpu.share to 2 for
revocable tasks (6).png, Performance improvement after reducing cpu.share to 2 for revocable
tasks (7).png, Performance improvement after reducing cpu.share to 2 for revocable tasks (8).png,
Performance improvement after reducing cpu.share to 2 for revocable tasks (9).png
>
>
> 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