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

Qian Zhang edited comment on MESOS-4392 at 1/18/16 2:25 PM:
------------------------------------------------------------

{quote}
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.
{quote}
So that means the oversubscribed resources (reported by resource estimator) 
should always be used by framework as revocable resources, but for the 
resources set aside to satisfy quota, they can be temporarily used by framework 
of not-quota'ed role as revocable resources, and once the framework of quota'ed 
role needs them, we should revoke them from the framework of not-quota'ed role 
and offer them to the framework of quota'ed role as non-revocable resources 
(i.e., we need to convert them from revocable to non-revocable), right?


was (Author: qianzhang):
{quote}
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.
{quote}
So that means the oversubscribed resources (reported by resource estimator) 
should always be used by framework as revocable resources, but for the 
resources set aside to satisfy quota, they can temporarily used by framework of 
not-quota'ed role as revocable resources, and once the framework of quota'ed 
role needs them, we should revoke them from the framework of not-quota'ed role 
and offer them to the framework of quota'ed role as non-revocable resources, 
right?

> 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