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

Fan Du commented on MESOS-3765:
-------------------------------

[~gyliu] The proposal document states "DRF will be disabled with Fine-Grained 
Resource Offers." , I am wondering why fine grained offer should bypass WDRF in 
practice? 

By my understanding, impliments fine grained offer fits well inside current 
WDRF logic, because of current allocation behavior:
Foreach Slave
   Foreach Role
     Foreach Framework within the role
         compute agent resources of revocable case OR
         compute agent resources of non-revocable case      <- (*A)
         offer the agent resources to current framework         <- (*B)

Each slave will grant at most one time allocation offer for the first framework 
within a role, if there is no revocalbe frameworks;
Each slave will grant at most two times allocations offer for one non-revocable 
and one revocalbe framework.

If we apply granuality between (*A) and (*B), it would be perfet to make loops 
to iterate remaining framworks,
the the goal to spread agent resource between frameworks is done.







> 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
>            Assignee: Guangya Liu
>
> 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