mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Weathers (JIRA)" <>
Subject [jira] [Commented] (MESOS-1807) Disallow executors with cpu only or memory only resources
Date Tue, 28 Jul 2015 19:05:06 GMT


Erik Weathers commented on MESOS-1807:

[]: 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:
>             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

This message was sent by Atlassian JIRA

View raw message