[
https://issues.apache.org/jira/browse/MESOS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14982172#comment-14982172
]
Klaus Ma commented on MESOS-1807:
---------------------------------
[[email protected]]/[~bmahler], I'd like to contribute to this ticket as it
seems related with MESOS-2845. But there're some question to this ticket:
- how do we define "0"? there're several tickets about checking scalar
against "0", e.g. MESOS-1187. I'd suggest to define the min cpu/mem, and check
executor's resources against mins.
- for the executor, it seems we're going to cover two cases:
1. executor & task runner is different: so we need assign resources to
both; if it's true, maybe we need to assign resources to command executor in
MESOS-2845; we need to evaluate the resource consumption of command line
executor.
2. executor & task runner is the same one; we plus the resources of them
> 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
> Attachments: Screenshot 2015-07-28 14.40.35.png
>
>
> 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)
