[
https://issues.apache.org/jira/browse/MESOS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596851#comment-14596851
]
Vinod Kone commented on MESOS-1807:
-----------------------------------
There seems to be some confusion, so let me clairfy.
Mesos currently allows executors that use either 0 cpus or 0 memory. Since
0.21.0, it emits a warning, but continues to allow them. Note that this ticket
is not resolved yet. The goal of this ticket is to disallow executors with 0
cpus or 0 memory.
Any issues that marathon or chronos are seeing is the long standing behavior of
Mesos and precisely why this ticket was created.
This deprecation was announced in the CHANGELOG for 0.21.0. Not sure if there
was a specific email sent to the dev list though.
> 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)
