[
https://issues.apache.org/jira/browse/MESOS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965245#comment-14965245
]
Guangya Liu commented on MESOS-3765:
------------------------------------
I think that the final goal is "fine-grained" resource scheduling and enabling
the master/allocator know the exact resource request is a easy way to implement
this. ;-)
Another point is that a framework hoard resources, do you mean the the
allocator can use filter to hoard resources for a framework? But the problem is
that the current filter is host level and even after filter expires, the
allocator still using the allocation unit to allocate resource offers and this
may still cannot satisfy the framework request. With "granularity", we may need
to set the filter to allocation unit level but not host level.
> 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)
