You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anindya Sinha (JIRA)" <ji...@apache.org> on 2016/10/03 17:57:20 UTC

[jira] [Updated] (MESOS-4666) Expose total resources of a slave in offer for scheduling decisions

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

Anindya Sinha updated MESOS-4666:
---------------------------------
    Assignee:     (was: Anindya Sinha)

> Expose total resources of a slave in offer for scheduling decisions
> -------------------------------------------------------------------
>
>                 Key: MESOS-4666
>                 URL: https://issues.apache.org/jira/browse/MESOS-4666
>             Project: Mesos
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: 0.25.0
>            Reporter: Anindya Sinha
>            Priority: Minor
>
> To effectively schedule certain class of tasks, the scheduler might need to know not only the available resources (as exposed currently) but also the maximum resources available on that slave. This is specifically true for clusters having different configurations of the slave nodes in terms of resources such as cpu, memory, disk, etc.
> Certain class of tasks might have a need to be scheduled on the same slave (esp needing shared persistent volumes, MESOS-3421). Instead of dedicating a slave to a framework, the framework can make a very good determination if it had exposure to both available as well as total resources.



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