mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Rukletsov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-3765) Make offer size adjustable (granularity)
Date Tue, 20 Oct 2015 14:50:27 GMT

    [ https://issues.apache.org/jira/browse/MESOS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965213#comment-14965213
] 

Alexander Rukletsov commented on MESOS-3765:
--------------------------------------------

{quote}
There might be problems that the master/allocator do not know the exact resource request of
the framework, so it seems difficult to let master/allocator satisfy the request of the framework
{quote}
But this is true for the status quo, right? Currently the allocator does not take into consideration
frameworks resource wishes, if any. This ticket proposes to make the "allocation chunk" adjustable.
IIUC, your proposal is to implement {{requestResources()}}, which is in my opinion is a separate
discussion. Also note that a framework may hoard resources, which means having multiple smaller
chunks should not be a big problem.

> 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)

Mime
View raw message