[ https://issues.apache.org/jira/browse/MESOS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970104#comment-14970104 ]
Klaus Ma commented on MESOS-3765: --------------------------------- But how to define the "allocation chunk"? For example, two framework(f1 and f2), each of them have a task acquire 1 CPU; one slave with only 1 CPU. I think we need a way to let allocator know the minimal resource requirement: by {{requestResources()}} or by {{filter}}. The framework can NOT define the resource requirement ahead because it dependent on the pending workload in it. > 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)