[
https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180819#comment-14180819
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-6052:
----------------------------------------------------
With your proposal, user has to set (1) log4j.configuration to the log-file
name (a very weird configuration) and then (2) explicitly add the log-file to
distributed cache.
I am proposing that we simply have (0) _mapreduce.job.log4j-configuration-file_
set to file:///home/vinodkv/container-log4j.properties#my-short-name which is
then recognized by JobClient, automatically uploaded to HDFS similar to job.jar
if it is a local file, and also added to distributed cache.
> 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)
