mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kone (JIRA)" <>
Subject [jira] [Updated] (MESOS-1807) Disallow executors with cpu only or memory only resources
Date Tue, 10 Feb 2015 18:53:12 GMT


Vinod Kone updated MESOS-1807:
    Target Version/s: 0.23.0  (was: 0.22.0)

I don't have cycles to work on this. Bumped the target version.

> Disallow executors with cpu only or memory only resources
> ---------------------------------------------------------
>                 Key: MESOS-1807
>                 URL:
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Vinod Kone
>            Assignee: Vinod Kone
>              Labels: newbie
> 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