You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Bernd Mathiske (JIRA)" <ji...@apache.org> on 2014/05/29 20:03:02 UTC
[jira] [Commented] (MESOS-1119) Allocator should make an allocation
decision per slave instead of per framework/role.
[ https://issues.apache.org/jira/browse/MESOS-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012629#comment-14012629 ]
Bernd Mathiske commented on MESOS-1119:
---------------------------------------
Can you elaborate on the reasons for this change and the specifics, please? How does your proposal work better and why? Pointers to literature? DRF = Dominant Resource Fairness?
> Allocator should make an allocation decision per slave instead of per framework/role.
> -------------------------------------------------------------------------------------
>
> Key: MESOS-1119
> URL: https://issues.apache.org/jira/browse/MESOS-1119
> Project: Mesos
> Issue Type: Bug
> Components: allocation
> Reporter: Vinod Kone
> Fix For: 0.19.0
>
>
> Currently the Allocator::allocate() code loops through roles and frameworks (based on DRF sort) and allocates *all* slaves resources to the first framework.
> This logic should be a bit inversed. Instead, the slave should go through each slave, allocate it a role/framework and update the DRF shares.
--
This message was sent by Atlassian JIRA
(v6.2#6252)