You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2015/05/14 04:26:59 UTC

[jira] [Issue Comment Deleted] (MESOS-2651) Implement QoS controller

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

Jie Yu updated MESOS-2651:
--------------------------
    Comment: was deleted

(was: commit d5dc043f1e8b4e3a7c7b4df69f865afdaeb0924b
Author: Jie Yu <yu...@gmail.com>
Date:   Wed May 6 15:30:55 2015 -0700

    Added resources estimator abstraction for oversubscription.
    
    Review: https://reviews.apache.org/r/33918)

> Implement QoS controller
> ------------------------
>
>                 Key: MESOS-2651
>                 URL: https://issues.apache.org/jira/browse/MESOS-2651
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Vinod Kone
>            Assignee: Niklas Quarfot Nielsen
>              Labels: mesosphere
>
> This is a component of the slave that informs the slave about the possible "corrections" that need to be performed (e.g., shutdown container using recoverable resources).
> This needs to be integrated with the resource monitor.
> Need to figure out the metrics used for sending corrections (e.g., scheduling latency, usage, informed by executor/scheduler)
> We also need to figure out the feedback loop between the QoS controller and the Resource Estimator.
> {code}
> class QoSController {
> public:
>   QoSController(ResourceMonitor* monitor);
>   process::Queue<QoSCorrection> correction();
> };
> {code}



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