You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2014/09/09 03:01:28 UTC
[jira] [Commented] (MESOS-1592) Design inverse resource offer
support
[ https://issues.apache.org/jira/browse/MESOS-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126421#comment-14126421 ]
Benjamin Mahler commented on MESOS-1592:
----------------------------------------
Moving this to reviewable as inverse offers were designed as part of the maintenance work: MESOS-1474.
We are currently considering how persistent resources will interact with inverse offers and the other maintenance primitives.
> 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: Alexandra Sava
>
> 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.3.4#6332)