You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Dominic Hamon (JIRA)" <ji...@apache.org> on 2014/08/04 21:24:11 UTC
[jira] [Updated] (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:all-tabpanel ]
Dominic Hamon updated MESOS-1119:
---------------------------------
Sprint: Q3 Sprint 1, Q3 Sprint 2 (was: Q3 Sprint 1, Q3 Sprint 2)
> 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
> Assignee: Vinod Kone
>
> 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)