[
https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254995#comment-16254995
]
Yufei Gu edited comment on YARN-7363 at 11/16/17 9:24 AM:
----------------------------------------------------------
Patch v1 does these things for process {{ContainerLocalizer}}.
* sets file "container-log4j.properties" as the log4j configuration.
* reuses the appender CLA in "container-log4j.properties".
* sets the ContainerLocalizer's log file name to "container-localizer-syslog"
was (Author: yufeigu):
Patch v1
* sets file "container-log4j.properties" as the log4j configuration.
* reuses the appender CLA in "container-log4j.properties".
* sets the ContainerLocalizer's log file name to "container-localizer-syslog"
> ContainerLocalizer don't have a valid log4j config in case of Linux container
> executor
> --------------------------------------------------------------------------------------
>
> 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
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
