[
https://issues.apache.org/jira/browse/MESOS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Downes resolved MESOS-1454.
-------------------------------
Resolution: Fixed
https://reviews.apache.org/r/22251
commit 75798d437f5f1f7d08b61388c9f1018a54553908
Author: Ian Downes <idow...@twitter.com>
Date: Wed Jun 4 16:19:54 2014 -0700
> Command executor should have nonzero resources
> ----------------------------------------------
>
> Key: MESOS-1454
> URL: https://issues.apache.org/jira/browse/MESOS-1454
> Project: Mesos
> Issue Type: Bug
> Reporter: Ian Downes
> Assignee: Ian Downes
>
> The command executor is used when TaskInfo does not provide an ExecutorInfo.
> It is not given any dedicated resources but the executor will be launched
> with the first task's resources. However, assuming a single task (or a final
> task), when that task terminates the container will be updated to zero
> resources - see containerizer->update in Slave::statusUpdate().
> Possible solutions:
> - Require a task to specify an executor and resources for it.
> - Add sufficient allowance for the command executor beyond the task's
> resources. This leads to an overcommit.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
