[
https://issues.apache.org/jira/browse/MESOS-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017860#comment-14017860
]
Ian Downes commented on MESOS-886:
----------------------------------
We're currently fixing this for task termination, see MESOS-1417. We're
splitting the statusUpdate() and likely going to destroy the container if the
update fails.
> Slave should wait until resources are isolated before launching tasks
> ---------------------------------------------------------------------
>
> Key: MESOS-886
> URL: https://issues.apache.org/jira/browse/MESOS-886
> Project: Mesos
> Issue Type: Bug
> Components: isolation, slave
> Affects Versions: 0.14.0
> Reporter: Ian Downes
> Priority: Minor
>
> The slave dispatches to the isolator to update resources and then sends
> RunTaskMessage to the executor without waiting for the update to complete.
> This race could, for example, lead to the task using too much RAM (including
> file cache) and then being OOM killed whenever the resource update completes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
