mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kone (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-1086) DRF allocator should take into account past allocations when determining an ordering so frameworks are not starved.
Date Tue, 01 Apr 2014 17:41:15 GMT

     [ https://issues.apache.org/jira/browse/MESOS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kone updated MESOS-1086:
------------------------------

    Fix Version/s:     (was: 0.19.0)
                   0.18.0

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

Mime
View raw message