[ https://issues.apache.org/jira/browse/MESOS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644829#comment-14644829 ]
Erik Weathers edited comment on MESOS-1807 at 7/28/15 6:42 PM: --------------------------------------------------------------- In mesos-0.20.1 the mesos UI got completely broken if you had fractional CPUs assigned to executors/tasks: * https://issues.apache.org/jira/secure/attachment/12747600/Screenshot%202015-07-28%2014.40.35.png I would consider that bug a "must fix" before disallowing 0 CPUs for executors. Maybe it's already fixed? was (Author: erikdw): In mesos-0.20.1 the mesos UI got completely broken if you had fractional CPUs assigned to executors/tasks: * https://issues.apache.org/jira/secure/attachment/12747600/Screenshot%202015-07-28%2014.40.35.png) I would consider that bug a "must fix" before disallowing 0 CPUs for executors. Maybe it's already fixed? > 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)