mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriel Hartmann (JIRA)" <>
Subject [jira] [Commented] (MESOS-3202) Avoid frameworks starving in DRF allocator.
Date Tue, 13 Sep 2016 04:01:20 GMT


Gabriel Hartmann commented on MESOS-3202:

Why is this resolved?  Frameworks are still starved.  See:

The proposed solution to dynamically change `refuse seconds` out of band is not a good way
to do cooperative scheduling.

> Avoid frameworks starving in DRF allocator.
> -------------------------------------------
>                 Key: MESOS-3202
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Joerg Schad
> We currently run into issues with the DRF scheduler that frameworks do not receive offers
(see for details). 
> Imagine that we have 10 frameworks and unallocated resources from a single slave.
> Allocation interval is 1 sec, and refuse_seconds (i.e. the time for which a declined
resource is filtered) is 3 sec across all frameworks. 
> Allocator offers resources to framework 1 (according to DRF) which declines the offer
> In the next allocation interval framework 1 is skipped due to the declined offer before.
Hence the next framework 2 is offered the resources, which it also declines.
> The same procedure in the next allocation interval (with framework 3). 
> In the next allocation interval the refuse_seconds for framework 1 are over, and as it
still has the lowest DRF share it gets the resource offered again, which it again declines.
And the cycle begins again....
> Framework 4 (which is actually waiting for this resource) is never offered this resource.

This message was sent by Atlassian JIRA

View raw message