[
https://issues.apache.org/jira/browse/MESOS-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432190#comment-15432190
]
Guangya Liu commented on MESOS-3078:
------------------------------------
The review posted by [~jjanco] here https://reviews.apache.org/r/51027/ can
help this, we can use similar logic in {{addSlave}} to handle this.
{code}
allocationCandidates.insert(slaveId);
if (!allocationPending) {
allocationPending = true;
dispatch(self(), &Self::allocate);
}
{code}
> 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
>
> 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)
