[
https://issues.apache.org/jira/browse/MESOS-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959697#comment-14959697
]
Vinod Kone commented on MESOS-2647:
-----------------------------------
Available revocable resources can change at any time because it is typically
based on the current utilization of the agent. This is different from regular
resources, whose availability only changes when tasks are launched/terminated.
For example, if the agent offers 2 cpus as revocable and a framework launches a
revocable task with 2 cpus, it might happen that just before the agent receives
the new revocable task, the utilization increased on the agent and the latest
available revocable estimate is 1 cpus.
> Slave should validate tasks using oversubscribed resources
> ----------------------------------------------------------
>
> Key: MESOS-2647
> URL: https://issues.apache.org/jira/browse/MESOS-2647
> Project: Mesos
> Issue Type: Task
> Reporter: Vinod Kone
> Assignee: Guangya Liu
> Labels: twitter
>
> The latest oversubscribed resource estimate might render a revocable task
> launch invalid. Slave should check this and send TASK_LOST with appropriate
> REASON.
> We need to add a new REASON for this (REASON_RESOURCE_OVERSUBSCRIBED?).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
