[
https://issues.apache.org/jira/browse/MESOS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Hindman resolved MESOS-1086.
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.19.0
commit 1fefd138159673ed0cf3b25538fe12b6e3917c59
Author: Benjamin Hindman <[email protected]>
Date: Tue Mar 11 22:00:17 2014 -0700
Enhanced DRF by including past allocations.
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.
Review: 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
> Fix For: 0.19.0
>
>
> 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)