[
https://issues.apache.org/jira/browse/MESOS-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100050#comment-16100050
]
Joris Van Remoortere commented on MESOS-3009:
---------------------------------------------
from: [http://man7.org/linux/man-pages/man5/systemd.resource-control.5.html]
{quote}Turns on delegation of further resource control partitioning to
processes of the unit. For unprivileged services (i.e. those
using the User= setting), this allows processes to create a
subhierarchy beneath its control group path. For privileged
services and scopes, this ensures the processes will have all
control group controllers enabled.{quote}
Systemd has started implementing the linux kernel goal of making the cgroup
file hierarchy read only. Sometimes it rebalances the cgroups hierarchy. If
there are settings (files) in there that were not initiated by it then it may
delete them if a rebalancing event occurs. One way to prevent this is to notify
systemd that you want to control the subhierarchy for your specific systemd
unit.
> Reproduce systemd cgroup behavior
> ----------------------------------
>
> Key: MESOS-3009
> URL: https://issues.apache.org/jira/browse/MESOS-3009
> Project: Mesos
> Issue Type: Task
> Reporter: Artem Harutyunyan
> Assignee: Joris Van Remoortere
> Labels: mesosphere
>
> It has been noticed before that systemd reorganizes cgroup hierarchy created
> by mesos slave. Because of this mesos is no longer able to find the cgroup,
> and there is also a chance of undoing the isolation that mesos slave puts in
> place.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
