You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Klaus Ma (JIRA)" <ji...@apache.org> on 2016/01/05 02:50:39 UTC

[jira] [Assigned] (MESOS-3078) Recovered resources are not re-allocated until the next allocation delay.

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

Klaus Ma reassigned MESOS-3078:
-------------------------------

    Assignee: Klaus Ma

> Recovered resources are not re-allocated until the next allocation delay.
> -------------------------------------------------------------------------
>
>                 Key: MESOS-3078
>                 URL: https://issues.apache.org/jira/browse/MESOS-3078
>             Project: Mesos
>          Issue Type: Improvement
>          Components: allocation
>            Reporter: Benjamin Mahler
>            Assignee: Klaus Ma
>
> Currently, when resources are recovered, we do not perform an allocation for that slave. Rather, we wait until the next allocation interval.
> For small task, high throughput frameworks, this can have a significant impact on overall throughput, see the following thread:
> http://markmail.org/thread/y6mzfwzlurv6nik3
> We should consider immediately performing a re-allocation for the slave upon resource recovery.



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