You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Dominic Hamon (JIRA)" <ji...@apache.org> on 2014/08/11 20:56:13 UTC

[jira] [Updated] (MESOS-1592) Design inverse resource offer support

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

Dominic Hamon updated MESOS-1592:
---------------------------------

    Story Points: 5
         Summary: Design inverse resource offer support  (was: Introduce the notion of an inverse resource offer.)

Added 5 as story point to capture uncertainty. Also renamed to more specifically describe the work here. Please add more tasks once the design is understood or if work needs to be done to complete the design.

> Design inverse resource offer support
> -------------------------------------
>
>                 Key: MESOS-1592
>                 URL: https://issues.apache.org/jira/browse/MESOS-1592
>             Project: Mesos
>          Issue Type: Task
>          Components: allocation
>            Reporter: Benjamin Mahler
>            Assignee: Benjamin Mahler
>
> An "inverse" resource offer means that Mesos is requesting resources back from the framework, possibly within some time interval.
> This can be leveraged initially to provide more automated cluster maintenance, by offering schedulers the opportunity to move tasks to compensate for planned maintenance. Operators can set a time limit on how long to wait for schedulers to relocate tasks before the tasks are forcibly terminated.
> Inverse resource offers have many other potential uses, as it opens the opportunity for the allocator to attempt to move tasks in the cluster through the co-operation of the framework, possibly providing better over-subscription, fairness, etc.



--
This message was sent by Atlassian JIRA
(v6.2#6252)