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

Bernd Mathiske commented on MESOS-4392:
---------------------------------------

Except for you last sentence, which I do not understand, I agree. It makes 
sense if a framework uses only non-revocable resources up to its quota. Note 
that if it does not set a quota limit, it can still use resources beyond its 
guarantee and those resources we now want to be revocable by default.

> Balance quota frameworks with non-quota, greedy frameworks.
> -----------------------------------------------------------
>
>                 Key: MESOS-4392
>                 URL: https://issues.apache.org/jira/browse/MESOS-4392
>             Project: Mesos
>          Issue Type: Epic
>          Components: allocation, master
>            Reporter: Bernd Mathiske
>            Assignee: Alexander Rukletsov
>              Labels: mesosphere
>
> Maximize resource utilization and minimize starvation risk for both quota 
> frameworks and non-quota, greedy frameworks when competing with each other.
> A greedy analytics batch system wants to use as much of the cluster as 
> possible to maximize computational throughput. When a competing web service 
> with fixed task size starts up, there must be sufficient resources to run it 
> immediately. The operator can reserve these resources by setting quota. 
> However, if these resources are kept idle until the service is in use, this 
> is wasteful from the analytics job's point of view. On the other hand, the 
> analytics job should hand back reserved resources to the service when needed 
> to avoid starvation of the latter.
> We can assume that often, the resources needed by the service will be of the 
> non-revocable variety. Here we need to introduce clearer distinctions between 
> oversubscribed and revocable resources that are not oversubscribed. An 
> oversubscribed resource cannot be converted into a non-revocable resource, 
> not even by preemption. In contrast, a non-oversubscribed, revocable resource 
> can be converted into a non-revocable resource.
> Another related topic is optimistic offers. The pertinent aspect in this 
> context is again whether resources are oversubscribed or not.



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

Reply via email to