[jira] [Assigned] (YARN-4030) Make Nodemanager cgroup usage for container easier to use when its running inside a cgroup

["Anubhav Dhoot (JIRA)" <ji...@apache.org>]

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

Anubhav Dhoot reassigned YARN-4030:
-----------------------------------

    Assignee:     (was: Anubhav Dhoot)

> Make Nodemanager cgroup usage for container easier to use when its running inside a cgroup 
> -------------------------------------------------------------------------------------------
>
>                 Key: YARN-4030
>                 URL: https://issues.apache.org/jira/browse/YARN-4030
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>            Reporter: Anubhav Dhoot
>
> Today nodemanager uses the cgroup prefix pointed by yarn.nodemanager.linux-container-executor.cgroups.hierarchy (default value /hadoop-yarn) directly at the path of the controller say /sys/fs/cgroup/cpu/hadoop-yarn. 
> If there are nodemanagers running inside docker containers on a host, each would typically be separated by a cgroup under the controller path say
> /sys/fs/cgroup/cpu/docker/<dockerid1>/nmcgroup for NM1 and /sys/fs/cgroup/cpu/docker/<dockerid2>/nmcgroup for NM2. 
> In this case the correct behavior should be to use the docker cgroup paths as 
> /sys/fs/cgroup/cpu/docker/<dockerid1>/hadoop-yarn for NM1
> /sys/fs/cgroup/cpu/docker/<dockerid2>/hadoop-yarn for NM2.
> But the default behavior would make both NMs try to use /sys/fs/cgroup/cpu/hadoop-yarn which is incorrect and would usually fail based on the permissions setup.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org