[
https://issues.apache.org/jira/browse/MESOS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973028#comment-14973028
]
Alexander Rukletsov edited comment on MESOS-3765 at 10/25/15 4:54 AM:
----------------------------------------------------------------------
Let's briefly touch that during the next community sync. I would like to figure
out whether it makes sense to jump on that before we refactor the allocator.
Also which working group should take care of this and who will shepherd.
was (Author: alexr):
Let's briefly touch that during the next sync. I would like to figure out
whether it makes sense to jump on that before we refactor the allocator. Also
which working group should take care of this and who will shepherd.
> 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)
