You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Ian Downes (JIRA)" <ji...@apache.org> on 2014/02/19 23:21:19 UTC
[jira] [Updated] (MESOS-996) Refactor linux/cgroups functions for
separate subsystem mounts.
[ https://issues.apache.org/jira/browse/MESOS-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Downes updated MESOS-996:
-----------------------------
Description:
0.18.0 requires each cgroup subsystem to be mounted separately, e.g., a container's cgroup would be:
{noformat}
{cgroups_hierarchy}/cpu/{cgroups_root}/container1
{noformat}
It would be much cleaner if the cgroups abstraction understood this and generally worked with the 3-tuple (hierarchy, subsystem, cgroup) rather than the existing tuple (hierarchy, cgroup).
was:
0.18.0 requires each cgroup subsystem to be mounted separately, e.g., a container's cgroup would be:{cgroups_hierarchy}/cpu/{cgroups_root}/container1
It would be much cleaner if the cgroups abstraction understood this and generally worked with the 3-tuple (hierarchy, subsystem, cgroup) rather than the existing tuple (hierarchy, cgroup).
> Refactor linux/cgroups functions for separate subsystem mounts.
> ---------------------------------------------------------------
>
> Key: MESOS-996
> URL: https://issues.apache.org/jira/browse/MESOS-996
> Project: Mesos
> Issue Type: Improvement
> Components: isolation
> Affects Versions: 0.18.0
> Reporter: Ian Downes
> Priority: Minor
>
> 0.18.0 requires each cgroup subsystem to be mounted separately, e.g., a container's cgroup would be:
> {noformat}
> {cgroups_hierarchy}/cpu/{cgroups_root}/container1
> {noformat}
> It would be much cleaner if the cgroups abstraction understood this and generally worked with the 3-tuple (hierarchy, subsystem, cgroup) rather than the existing tuple (hierarchy, cgroup).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)