[
https://issues.apache.org/jira/browse/MESOS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972957#comment-14972957
]
Guangya Liu commented on MESOS-3765:
------------------------------------
[~alexr] I think that your original thought is enable cluster level, when start
up mesos master, the cluster operator can define the "granularity" or
"allocation unit" for all of the frameworks.
After a second thought, I think that the "granularity" should be defined by the
framework as only the framework knows how many resource does he want, each
framework can just define its "granularity" or "allocation unit" to its task
size (or else we can treat the task size as allocation unit) and request
resource to Mesos via `requestResources()`, the mesos master will help
calculate if the requirement can be satisfied and launch task accordingly. I
think that this is the best way to achieve the "granularity".
> 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)
