[
https://issues.apache.org/jira/browse/MESOS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596807#comment-14596807
]
Elizabeth Lingg commented on MESOS-1807:
----------------------------------------
For me, the issue is that Chronos and Marathon, for example, currently launch
custom executors with 0 cpu AND 0 memory. While this needs to be fixed in
Chronos and Marathon, a full announcement, warning, deprecation cycle would be
appropriate in my view.
I do agree that custom executors need to specify both CPU and 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)
