You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2015/05/15 23:00:00 UTC

[jira] [Commented] (MESOS-2734) Update allocator to allocate revocable resources

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

Niklas Quarfot Nielsen commented on MESOS-2734:
-----------------------------------------------

Should we break this down into smaller pieces? Maybe include a ticket for documenting the semantic changes?

> Update allocator to allocate revocable resources
> ------------------------------------------------
>
>                 Key: MESOS-2734
>                 URL: https://issues.apache.org/jira/browse/MESOS-2734
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Vinod Kone
>              Labels: twitter
>
> Allocator maintains 'revocable' resources which keeps track of the currently available revocable resources.
> Revocable resources are added to the DRF sorter allocations much like regular resources during recoverResources() and allocate().
> The only difference is that, unlike regular resources, 'revocable' resources are *not* updated in allocate() or recover(). They only get updated in updateRevocableResources() call.
> The 2 main consequences of this design are
> --> Revocable resources are accounted for in fair sharing which is great.
> --> Allocation for revocable resources only happens whenever there is a new estimate from the slave.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)