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

Guangya Liu edited comment on MESOS-3765 at 10/20/15 2:40 PM:
--------------------------------------------------------------

There might be problems that the master/allocator do not know the exact 
resource request of the framework, so it seems difficult to let 
master/allocator satisfy the request of the framework and sometimes this may 
cause the framework starve if the offer do not have enough resources.

Mesos now support {code}requestResource{code}, can we leverage this API? The 
framework can just send the exact resource request to Mesos master and the 
master can return the offer with the exact request resource to framework, 
comments?


was (Author: gyliu):
There might be problems that the master/allocator do not know the exact 
resource request of the framework, so it seems difficult to let 
master/allocator satisfy the request of the framework and sometimes this may 
cause the framework starve if the offer do not have enough resources.

Mesos now support requestResource, can we leverage this API? The framework can 
just send the exact resource request to Mesos master and the master can return 
the offer with the exact request resource to framework, comments?

> Make offer size adjustable (granularity)
> ----------------------------------------
>
>                 Key: MESOS-3765
>                 URL: https://issues.apache.org/jira/browse/MESOS-3765
>             Project: Mesos
>          Issue Type: Improvement
>          Components: allocation
>            Reporter: Alexander Rukletsov
>
> The built-in allocator performs "coarse-grained" allocation, meaning that it 
> always allocates the entire remaining agent resources to a single framework. 
> This may heavily impact allocation fairness in some cases, for example in 
> presence of numerous greedy frameworks and a small number of powerful agents.
> A possible solution would be to allow operators explicitly specify 
> granularity via allocator flags. While this can be tricky for non-standard 
> resources, it's pretty straightforward for {{cpus}} and {{mem}}.



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

Reply via email to