You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2014/09/17 20:32:33 UTC

[jira] [Created] (MESOS-1807) Disallow executors with cpu only or memory only resources

Vinod Kone created MESOS-1807:
---------------------------------

             Summary: Disallow executors with cpu only or memory only resources
                 Key: MESOS-1807
                 URL: https://issues.apache.org/jira/browse/MESOS-1807
             Project: Mesos
          Issue Type: Improvement
            Reporter: Vinod Kone


Currently master allows executors to be launched with either only cpus or only memory but we shouldn't allow that.
This is because executor is an actual unix process that is launched by the slave. If an executor doesn't specify cpus, what should do the cpu limits be for that executor when there are no tasks running on it? If no cpu limits are set then it might starve other executors/tasks on the slave violating isolation guarantees. Same goes with memory. Moreover, the current containerizer/isolator code will throw failures when using such an executor, e.g., when the last task on the executor finishes and Containerizer::update() is called with 0 cpus or 0 mem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)