[
https://issues.apache.org/jira/browse/MESOS-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108651#comment-15108651
]
Guangya Liu commented on MESOS-4442:
------------------------------------
In T3, I think that master will recoverResources when updateSlave, the 1
revocable cpus should be returned back and thus the allocated will be decreased
to cpu(*):1, then how does T4 over-offer?
> Resource maybe over-offered if estimator shrunk un-used resources.
> ------------------------------------------------------------------
>
> Key: MESOS-4442
> URL: https://issues.apache.org/jira/browse/MESOS-4442
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: Klaus Ma
> Assignee: Klaus Ma
>
> Here's the time sequence of this issue:
> T1: in cluster, {{cpus=2}}: one 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.
> At T4, the state of allocator is in-correct (slave.total > slave.allocated).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
