[
https://issues.apache.org/jira/browse/MESOS-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106863#comment-15106863
]
Klaus Ma edited comment on MESOS-2930 at 1/19/16 3:21 PM:
----------------------------------------------------------
[~nnielsen], there's a case we need to handle regrading this JIRA:
* T1: in cluster, {{cpus=2}}: on is revocable and the other one is nonRevocable
* T2: {{framework1}} get offer {{cpus=2}}, but did NOT launch tasks
* T3: Estimator update empty resources; {{slave.total}} is updated to
{{cpus=1}} in {{HierarchicalAllocatorProcess::updateSlave}}
* T4: in {{allocate()}}, slave.total (cpus=1) < slave.allocated (cpus=2), the
resources {{cpus=1}} will re-offer to framework because {{operator-}} will
return first item if {{subtractable}} is false.
Any comments?
was (Author: klaus1982):
[~nnielsen], there's a case we need to handle regrading this JIRA:
* T1: in cluster, {{cpus=2}}: on is revocable and the other one is nonRevocable
* T2: {{framework1}} get offer {{cpus=2}}, but did NOT launch tasks
* T3: Estimator update empty resources; {{slave.total}} is updated to
{{cpus=1}} in {{HierarchicalAllocatorProcess::updateSlave}}
* T4: in {{allocate()}}, slave.total (cpus=1) < slave.allocated (cpus=2), the
resources {{cpus=1}} will re-offer to framework because {{operator-}} will
return first item is {{subtractable}} is false.
Any comments?
> Allow the Resource Estimator to express over-allocation of revocable
> resources.
> -------------------------------------------------------------------------------
>
> Key: MESOS-2930
> URL: https://issues.apache.org/jira/browse/MESOS-2930
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Benjamin Mahler
> Assignee: Klaus Ma
>
> Currently the resource estimator returns the amount of oversubscription
> resources that are available, since resources cannot be negative, this allows
> the resource estimator to express the following:
> (1) Return empty resources: We are fully allocated for oversubscription
> resources.
> (2) Return non-empty resources: We are under-allocated for oversubscription
> resources. In other words, some are available.
> However, there is an additional situation that we cannot express:
> (3) Analogous to returning non-empty "negative" resources: We are
> over-allocated for oversubscription resources. Do not re-offer any of the
> over-allocated oversubscription resources that are recovered.
> Without (3), the slave can only shrink the total pool of oversubscription
> resources by returning (1) as resources are recovered, until the pool is
> shrunk to the desired size. However, this approach is only best-effort, it's
> possible for a framework to launch more tasks in the window of time (15
> seconds by default) that the slave polls the estimator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
