You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Joris Van Remoortere (JIRA)" <ji...@apache.org> on 2015/09/01 17:09:45 UTC

[jira] [Updated] (MESOS-3352) Problem Statement Summary for Systemd Cgroup Launcher

     [ https://issues.apache.org/jira/browse/MESOS-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joris Van Remoortere updated MESOS-3352:
----------------------------------------
    Description: 
There have been many reports of cgroups related issues when running Mesos on Systemd.
Many of these issues are rooted in the manual manipulation of the cgroups filesystem by Mesos.
This task is to describe the problem in a 1-page summary, and elaborate on the suggested 2 part solution:
1. Using the {{delegate=true}} flag for the slave
2. Implementing a Systemd launcher to run executors with tighter Systemd integration.

  was:
There have been many reports of cgroups related issues when running Mesos on Systemd.
Many of these issues are rooted in the manual manipulation of the cgroups filesystem by Mesos.
This task is to describe the problem in a 1-page summary, and elaborate on the suggested 2 part solution:
1. Using the {delegate=true} flag for the slave
2. Implementing a Systemd launcher to run executors with tighter Systemd integration.


> Problem Statement Summary for Systemd Cgroup Launcher
> -----------------------------------------------------
>
>                 Key: MESOS-3352
>                 URL: https://issues.apache.org/jira/browse/MESOS-3352
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Joris Van Remoortere
>            Assignee: Joris Van Remoortere
>              Labels: design, mesosphere, systemd
>
> There have been many reports of cgroups related issues when running Mesos on Systemd.
> Many of these issues are rooted in the manual manipulation of the cgroups filesystem by Mesos.
> This task is to describe the problem in a 1-page summary, and elaborate on the suggested 2 part solution:
> 1. Using the {{delegate=true}} flag for the slave
> 2. Implementing a Systemd launcher to run executors with tighter Systemd integration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)