You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Ian Downes (JIRA)" <ji...@apache.org> on 2014/06/04 20:01:11 UTC

[jira] [Created] (MESOS-1454) Command executor should have nonzero resources

Ian Downes created MESOS-1454:
---------------------------------

             Summary: 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


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)