hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ray Chiang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-7363) ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor
Date Mon, 27 Nov 2017 22:33:00 GMT

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

Ray Chiang updated YARN-7363:
-----------------------------
    Summary: ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor
 (was: ContainerLocalizer don't have a valid log4j config in case of Linux container executor)

> ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-7363
>                 URL: https://issues.apache.org/jira/browse/YARN-7363
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 3.1.0
>            Reporter: Yufei Gu
>            Assignee: Yufei Gu
>         Attachments: YARN-7363.001.patch, YARN-7363.002.patch, YARN-7363.003.patch, YARN-7363.004.patch,
YARN-7363.005.patch
>
>
> In case of Linux container executor, ContainerLocalizer run as a separated process. It
doesn't access a valid log4j.properties when the application user is not in the "hadoop" group.
The log4j.properties of node manager is in its classpath, but it isn't readable by users not
in hadoop group due to the security concern. In that case, ContainerLocalizer doesn't have
a valid log4j configuration, and normally no log output.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message