You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Hindman (JIRA)" <ji...@apache.org> on 2014/03/12 06:06:43 UTC
[jira] [Assigned] (MESOS-1086) DRF allocator should take into
account past allocations when determining an ordering so frameworks are not
starved.
[ https://issues.apache.org/jira/browse/MESOS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Hindman reassigned MESOS-1086:
---------------------------------------
Assignee: Benjamin Hindman
https://reviews.apache.org/r/19090
> DRF allocator should take into account past allocations when determining an ordering so frameworks are not starved.
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MESOS-1086
> URL: https://issues.apache.org/jira/browse/MESOS-1086
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: Benjamin Hindman
> Assignee: Benjamin Hindman
> Priority: Critical
>
> The DRF allocator (master/drf_sorter.hpp|cpp) currently only uses a framework's share to determine an ordering for allocating resources. When there are very few resources to go around it's possible that a framework will get allocated resources (making it have a dominant share larger than others), use those resources, then return those resources (making it's dominant share equal to the share of others), and then get reallocated the resources _again_ because its dominant share is equal to others. This can cause starvation for frameworks.
--
This message was sent by Atlassian JIRA
(v6.2#6252)