[ https://issues.apache.org/jira/browse/MESOS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644867#comment-14644867 ]
Erik Weathers edited comment on MESOS-1807 at 7/28/15 8:27 PM: --------------------------------------------------------------- [~vi...@twitter.com]: without the web UI fix then to me its unacceptable to *use* fractional CPUs at all. So for storm-on-mesos I'm using "0" as the executor CPUs (because the mesos-supervisor does almost nothing, 0 is not entirely unreasonable). When the behavior change requested in this ticket is enacted (changing from warning to error) then I will either be stuck on the previous version of mesos, or I will be forced to have an ugly UI. My colleague found a couple of bugs that are related to this issue I'm mentioning: * MESOS-2635 * MESOS-1867 was (Author: erikdw): [~vi...@twitter.com]: without the web UI fix then to me its unacceptable to *use* fractional CPUs at all. So for storm-on-mesos I'm using "0" as the executor CPUs (because the mesos-supervisor does almost nothing, 0 is not entirely unreasonable). When the behavior change requested in this ticket is enacted (changing from warning to error) then I will either be stuck on the previous version of mesos, or I will be forced to have an ugly UI. > 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)