[
https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179407#comment-14179407
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-6052:
----------------------------------------------------
bq. Hi Vinod Kumar Vavilapalli, can you clarify more on this? I think user can
explicitly use the configuration of "-files log4j.properties" to add file to
distributed cached and deliver to each node. Right? So may be we should do here
is to add the parent directory of dc files to classpath by default. Attaching a
patch to demonstrate this.
It's weird that we are only letting users configure the _name_ of the log4j
config file but not letting them specify what the _file itself_ is. I'd rather
have an option to simply say "hey this is my log4j configuration file on HDFS,
go use it".
> 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)
