[
https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180935#comment-14180935
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-6052:
----------------------------------------------------
My proposal in concrete
- Add a new config _mapreduce.job.log4j-properties-uri_ or
_mapreduce.job.log4j-properties-file_.
- JobClient adds file this to distributed-cache, as a class-path file before
submission. The 'key' in distributed-cache is the same URI.
-- If _mapreduce.job.log4j-properties-uri_ is a local file-system URI, the
file automatically gets uploaded to HDFS and then gets distributed everywhere.
-- If it is a HDFS location, it is simply distributed everywhere via
dist-cache.
- MR AM reads the config property, and if it is set, appends
"-Dlog4j.configuration=$(file-name)". Here "file-name" is the path component of
uri or a URI fragment if present (this is the convention for distribute-cache
too).
> Support overriding log4j.properties per job
> -------------------------------------------
>
> Key: MAPREDUCE-6052
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6052
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Junping Du
> Assignee: Junping Du
> Attachments: MAPREDUCE-6052-v2.patch, MAPREDUCE-6052.patch
>
>
> For current MR application, the "log4j.configuration" is hard coded to
> container-log4j.properties within each node. We still need flexibility to
> override it per job like what we do in MRV1.
> {code}
> public static void addLog4jSystemProperties(
> String logLevel, long logSize, int numBackups, List<String> vargs) {
> vargs.add("-Dlog4j.configuration=container-log4j.properties");
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
