[
https://issues.apache.org/jira/browse/MAPREDUCE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246949#comment-14246949
]
Junping Du commented on MAPREDUCE-6149:
---------------------------------------
Thanks [~qwertymaniac] for review and comments! Address most of comments in v2
patch.
bq. 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.
That's true. Sorry for mistake here. Remove the misleading part.
bq. What impact does this have, if any, over the use of
mapreduce.map/reduce.log.level?
The config set in "mapreduce.map/reduce.log.level" could be overridden by
log4j.properties specified here. Already add the mention to related two
configuration in v2 patch.
bq. Are any standard logger names/configs required to be present, such that all
of our framework-side logging ends up finding a valid appender.
Not too much idea in my mind even after checking container-log4j.properties.
Any suggestions here?
> 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-v2.patch, 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)
