[
https://issues.apache.org/jira/browse/MAPREDUCE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246522#comment-14246522
]
Harsh J commented on MAPREDUCE-6149:
------------------------------------
Thanks for adding this to the default xml. I have a few questions that could be
addressed by a refactored description, so it may cover everything that a user
would need to do when using this:
- The statement {{container-log4j.properties under $HADOOP_CONF_DIR on each
node}} is a bit misleading, since the file is typically from within the jar
(hadoop-yarn-server-nodemanger.jar) and not usually on the service
$HADOOP_CONF_DIR paths.
- What impact does this have, if any, over the use of
mapreduce.map/reduce.log.level?
- Are any standard logger names/configs required to be present, such that all
of our framework-side logging ends up finding a valid appender?
> Document override log4j.properties in MR job
> --------------------------------------------
>
> Key: MAPREDUCE-6149
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6149
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: documentation
> Reporter: Junping Du
> Assignee: Junping Du
> Attachments: MAPREDUCE-6149.patch
>
>
> This new feature comes from MAPREDUCE-6052, some documentation requirements
> from Vinod below:
> Document the new config in mapred-default.xml
> Mention in that documentation that if no-scheme is given in the path, it
> defaults to a log4j file on the local FS.
> Modify the documentation of log-level configs to say that if you override
> to have your own log4j.properties file, the log-level configs may not work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
