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 "Varun Saxena (JIRA)" <ji...@apache.org> on 2016/07/26 16:06:20 UTC
[jira] [Updated] (YARN-5422) ContainerLocalizer log should be
logged in separate log file.
[ https://issues.apache.org/jira/browse/YARN-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Saxena updated YARN-5422:
-------------------------------
Assignee: Surendra Singh Lilhore
> ContainerLocalizer log should be logged in separate log file.
> -------------------------------------------------------------
>
> Key: YARN-5422
> URL: https://issues.apache.org/jira/browse/YARN-5422
> Project: Hadoop YARN
> Issue Type: Bug
> Components: applications
> Affects Versions: 2.7.1
> Reporter: Surendra Singh Lilhore
> Assignee: Surendra Singh Lilhore
>
> We should set the log4j for the ContainerLocalizer jvm. Currently it will use the NM log4j and it will log the logs in NM hadoop.log file.
> If NM user and application user is different, then ContainerLocalizer will not be able to log in hadoop.log file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org