You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Ray Chiang (JIRA)" <ji...@apache.org> on 2017/12/06 18:56:00 UTC
[jira] [Updated] (YARN-7363) ContainerLocalizer doesn't have a
valid log4j config when using LinuxContainerExecutor
[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ray Chiang updated YARN-7363:
-----------------------------
Fix Version/s: (was: 3.0.0)
3.0.1
> 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
> Fix For: 3.1.0, 2.10.0, 3.0.1
>
> Attachments: YARN-7363.001.patch, YARN-7363.002.patch, YARN-7363.003.patch, YARN-7363.004.patch, YARN-7363.005.patch, YARN-7363.branch-2.001.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