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

Guangya Liu edited comment on MESOS-6113 at 9/1/16 5:32 AM:
------------------------------------------------------------

MESOS-4967 is kind of oversubscription for reserved resources and MESOS-4392 is 
kind of oversubscription for quota resources. I was a bit confused here: The 
content in this JIRA is for {{Quota}} resources while the title is for 
{{reserved}} resources, can you elaborate? [~mgummelt]


was (Author: gyliu):
MESOS-4976 is kind of oversubscription for reserved resources and MESOS-4392 is 
kind of oversubscription for quota resources. I was a bit confused here: The 
content in this JIRA is for {{Quota}} resources while the title is for 
{{reserved}} resources, can you elaborate? [~mgummelt]

> Offer reserved resources as revocable
> -------------------------------------
>
>                 Key: MESOS-6113
>                 URL: https://issues.apache.org/jira/browse/MESOS-6113
>             Project: Mesos
>          Issue Type: Task
>          Components: allocation
>    Affects Versions: 1.0.1
>            Reporter: Michael Gummelt
>
> *Goal:*
> I have high-priority Spark jobs, and best-effort jobs.  I need my 
> high-priority jobs to pre-empt my best-effort jobs, so I'd like to launch the 
> best-effort jobs on revocable resources. 
> *Problem:*
> Revocable resources are currently only created via oversubscription, where 
> resources allocated to but not used by a framework will be offered to other 
> frameworks.  This doesn't support the ability for a high-pri framework to 
> start up and pre-empty a low-pri framework.
> *Solution:*
> Let's allow quota (and ideally any reserved resources) to be configurable to 
> be offered as revocable resources to other frameworks that don't register 
> with the role.



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

Reply via email to