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

["Adam B (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14594522#comment-14594522 ] 

Adam B commented on MESOS-1807:
-------------------------------

I'm confused.. are Spark/Marathon/Chronos failing already due to executors with 0 cpu AND 0 memory, and this ticket wants to also fail for 0 cpu OR 0 memory? Do we need to through an announcement/warning/deprecation cycle first?
Or is this issue to remove/relax the previous constraint so that frameworks will fail only with executors with 0 cpu XOR 0 memory?

> 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
>              Labels: newbie
>
> 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)