[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesos-issues
Subject:    [jira] [Commented] (MESOS-1807) Disallow executors with cpu only or memory only resources
From:       "Vinod Kone (JIRA)" <jira () apache ! org>
Date:       2015-10-30 16:36:27
Message-ID: JIRA.12742227.1410978695000.109567.1446222987794 () Atlassian ! JIRA
[Download RAW message or body]


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

Vinod Kone commented on MESOS-1807:
-----------------------------------

I think we need to first fix MESOS-1187 and MESOS-1718 before we tackle this ticket. \
I'll take a look at the latest discussion and add comments on the respective tickets.

> 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)


[prev in list] [next in list] [prev in thread] [next in thread]