[
https://issues.apache.org/jira/browse/MESOS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993679#comment-14993679
]
Qian Zhang commented on MESOS-3765:
-----------------------------------
Thanks [~adam-mesos], actually I am reviewing the patches of quota epic, but I
do not see how quota can be subdivided at least in the MVP, maybe what you are
talking about is chunk which we will implement it in the post-MVP?
And for weight, if we handle it in the way that you mentioned above, I think
actually we would have changed its original meaning / purpose, originally
weight is kind of share priority, but now we will want it to represent share
ratio, right?
> 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)
