You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2014/08/19 01:51:18 UTC

[jira] [Created] (MESOS-1718) Command executor can overcommit the slave.

Benjamin Mahler created MESOS-1718:
--------------------------------------

             Summary: Command executor can overcommit the slave.
                 Key: MESOS-1718
                 URL: https://issues.apache.org/jira/browse/MESOS-1718
             Project: Mesos
          Issue Type: Bug
          Components: slave
            Reporter: Benjamin Mahler


Currently we give a small amount of resources to the command executor, in addition to resources used by the command task:

https://github.com/apache/mesos/blob/0.20.0-rc1/src/slave/slave.cpp#L2448
{code: title=}
ExecutorInfo Slave::getExecutorInfo(
    const FrameworkID& frameworkId,
    const TaskInfo& task)
{
  ...
    // Add an allowance for the command executor. This does lead to a
    // small overcommit of resources.
    executor.mutable_resources()->MergeFrom(
        Resources::parse(
          "cpus:" + stringify(DEFAULT_EXECUTOR_CPUS) + ";" +
          "mem:" + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
  ...
}
{code}

This leads to an overcommit of the slave. Ideally, for command tasks we can "transfer" all of the task resources to the executor at the slave / isolation level.



--
This message was sent by Atlassian JIRA
(v6.2#6252)