[
https://issues.apache.org/jira/browse/MESOS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy St. Clair updated MESOS-1807:
-------------------------------------
Comment: was deleted
(was: Was the original goal of cpu+memory only offers to enable resizing? The
behavior change had caused other frameworks to fail, namely Spark.
Ideally I would love to have some integration testing on mods like this.
[~tnachen] ^
)
> 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
> Assignee: 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)
