[
https://issues.apache.org/jira/browse/MESOS-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaus Ma updated MESOS-4808:
----------------------------
Description: Currently, {{allocate()}} are executed every-time when a new
slave/framework are registered; if there're lots of agent start all most the
same time, the allocation will keep running for a while. It's acceptable
behaviour to allocate resources in next allocation cycle. But when a task is
finished, it's better to allocate ASAP although there's performances issues;
refer to MESOS-3078 for more detail on short running tasks. (was: Currently,
{{allocate()}} are executed every-time when a new slave/framework are
registered; if there're lots of agent start all most the same time, the
allocation will keep running for a while. It's acceptable behaviour to allocate
resources in next allocation cycle. But when a task is finished, it's better to
allocate ASAP; refer to MESOS-3078 for more detail on short running tasks.)
> Allocation in batch instead of execute it every-time when
> addSlave/addFramework.
> --------------------------------------------------------------------------------
>
> Key: MESOS-4808
> URL: https://issues.apache.org/jira/browse/MESOS-4808
> Project: Mesos
> Issue Type: Bug
> Components: allocation
> Reporter: Klaus Ma
> Labels: master, tech-debt
>
> Currently, {{allocate()}} are executed every-time when a new slave/framework
> are registered; if there're lots of agent start all most the same time, the
> allocation will keep running for a while. It's acceptable behaviour to
> allocate resources in next allocation cycle. But when a task is finished,
> it's better to allocate ASAP although there's performances issues; refer to
> MESOS-3078 for more detail on short running tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
