[jira] [Updated] (MAPREDUCE-6052) Support overriding log4j.properties per job

2014-10-25 Thread Junping Du (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Junping Du updated MAPREDUCE-6052:
--
Attachment: MAPREDUCE-6052-v3.patch

> 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-v3.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 vargs) {
> vargs.add("-Dlog4j.configuration=container-log4j.properties");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MAPREDUCE-6052) Support overriding log4j.properties per job

2014-10-25 Thread Junping Du (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184118#comment-14184118
 ] 

Junping Du commented on MAPREDUCE-6052:
---

Sounds good. In v3 patch, implement most as proposed above but updating 
JobSubmitter instead of JobClient as new mapreduce API (package with 
mapreduce.*) is more important for new feature. 


> 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-v3.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 vargs) {
> vargs.add("-Dlog4j.configuration=container-log4j.properties");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MAPREDUCE-6052) Support overriding log4j.properties per job

2014-10-25 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184168#comment-14184168
 ] 

Hadoop QA commented on MAPREDUCE-6052:
--

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12677109/MAPREDUCE-6052-v3.patch
  against trunk revision f44cf99.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4980//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4980//console

This message is automatically generated.

> 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-v3.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 vargs) {
> vargs.add("-Dlog4j.configuration=container-log4j.properties");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MAPREDUCE-6018) Create a framework specific config to enable timeline server

2014-10-25 Thread Vinod Kumar Vavilapalli (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184365#comment-14184365
 ] 

Vinod Kumar Vavilapalli commented on MAPREDUCE-6018:


Haven't looked at all of the patch, but one comment: How about 
{{mapreduce.job.emit-timeline-data}} (or something similar) instead of 
{{mapreduce.job.timeline-service.enabled}}? If you agree, similarly rename the 
constants.

> Create a framework specific config to enable timeline server
> 
>
> Key: MAPREDUCE-6018
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6018
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>Reporter: Jonathan Eagles
>Assignee: Robert Kanter
> Attachments: MAPREDUCE-6018.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MAPREDUCE-6018) Create a framework specific config to enable timeline server

2014-10-25 Thread Zhijie Shen (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184372#comment-14184372
 ] 

Zhijie Shen commented on MAPREDUCE-6018:


Let's say mapreduce.job.emit-timeline-data.enabled?

> Create a framework specific config to enable timeline server
> 
>
> Key: MAPREDUCE-6018
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6018
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>Reporter: Jonathan Eagles
>Assignee: Robert Kanter
> Attachments: MAPREDUCE-6018.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)