[jira] [Commented] (MAPREDUCE-6203) if log-aggregation is enable and run some MR job, the AM log will be aggregated.then disable it,then in MR JobHistoryServer and YARN RM UI link,the AM log cannot be

2014-12-24 Thread Brahma Reddy Battula (JIRA)

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

Brahma Reddy Battula commented on MAPREDUCE-6203:
-

HI huangyitian,

Turning on log aggregation allows users to easily store container logs in HDFS 
and subsequently view them in the YARN web UIs from a central place.

If  *yarn.log-aggregation-enable*  is disabled try looking for the logs under 
each nodemanager that ran the tasks. 
The location for this local dir is configured as property  
*yarn.nodemanager.log-dirs*  in yarn-site.xml

SO if you want to view from JHS and YARN Web UI then enable log aggregation..

> if log-aggregation is enable and run some MR job, the AM log will be 
> aggregated.then disable it,then in MR JobHistoryServer and YARN RM UI 
> link,the AM log cannot be visible
> 
>
> Key: MAPREDUCE-6203
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6203
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: jobhistoryserver
>Affects Versions: 2.4.1
>Reporter: huangyitian
>Priority: Minor
>
> as the Summary description, I think for the MR JobHistory Server, should not 
> let “yarn.log-aggregation-enable” affect the history job,even 
> “yarn.log-aggregation-enable” is false.



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


[jira] [Commented] (MAPREDUCE-6204) TestJobCounters should use new properties instead JobConf.MAPRED_TASK_JAVA_OPTS

2014-12-24 Thread Tsuyoshi OZAWA (JIRA)

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

Tsuyoshi OZAWA commented on MAPREDUCE-6204:
---

Sam, thanks for your clarification. 

+1 against MAPREDUCE-6204-1.patch with following reasons:
1. We should use new properties instead of deprecated one. 
2. On some environment, JVM options are configured wrongly. As a result, 
TestJobCounters can fails. The patch fix the problem.

[~jira.shegalov] please let me know if you have opinions.

> TestJobCounters should use new properties instead 
> JobConf.MAPRED_TASK_JAVA_OPTS
> ---
>
> Key: MAPREDUCE-6204
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6204
> Project: Hadoop Map/Reduce
>  Issue Type: Test
>  Components: test
>Affects Versions: 2.6.0
>Reporter: sam liu
>Assignee: sam liu
>Priority: Minor
> Attachments: MAPREDUCE-6204-1.patch, MAPREDUCE-6204.patch
>
>




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


[jira] [Commented] (MAPREDUCE-6205) Update the value of the new version properties of the deprecated property "mapred.child.java.opts"

2014-12-24 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on MAPREDUCE-6205:
--

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12689020/MAPREDUCE-6205.patch
  against trunk revision 4f18018.

{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:red}-1 findbugs{color}.  The patch appears to introduce 16 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:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-common-project/hadoop-common 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core:

  org.apache.hadoop.ha.TestZKFailoverControllerStress

Test results: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5091//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5091//artifact/patchprocess/newPatchFindbugsWarningshadoop-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5091//artifact/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-core.html
Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5091//console

This message is automatically generated.

> Update the value of the new version properties of the deprecated property 
> "mapred.child.java.opts"
> --
>
> Key: MAPREDUCE-6205
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6205
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: mrv2
>Affects Versions: trunk
>Reporter: sam liu
>Assignee: sam liu
>Priority: Minor
> Attachments: MAPREDUCE-6205.patch, MAPREDUCE-6205.patch
>
>
> In current hadoop code, the old property "mapred.child.java.opts" is 
> deprecated and its new versions are MRJobConfig.MAP_JAVA_OPTS and 
> MRJobConfig.REDUCE_JAVA_OPTS. However, when user set a value to the 
> deprecated property "mapred.child.java.opts", hadoop won't automatically 
> update its new versions properties 
> MRJobConfig.MAP_JAVA_OPTS("mapreduce.map.java.opts") and 
> MRJobConfig.REDUCE_JAVA_OPTS("mapreduce.reduce.java.opts"). As hadoop will 
> update the new version properties for many other deprecated properties, we 
> also should support such feature on the old property 
> "mapred.child.java.opts", otherwise it might bring some imcompatible issues.



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


[jira] [Updated] (MAPREDUCE-6205) Update the value of the new version properties of the deprecated property "mapred.child.java.opts"

2014-12-24 Thread sam liu (JIRA)

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

sam liu updated MAPREDUCE-6205:
---
Attachment: MAPREDUCE-6205.patch

Updated TestJobConf according the code changes

> Update the value of the new version properties of the deprecated property 
> "mapred.child.java.opts"
> --
>
> Key: MAPREDUCE-6205
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6205
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: mrv2
>Affects Versions: trunk
>Reporter: sam liu
>Assignee: sam liu
>Priority: Minor
> Attachments: MAPREDUCE-6205.patch, MAPREDUCE-6205.patch
>
>
> In current hadoop code, the old property "mapred.child.java.opts" is 
> deprecated and its new versions are MRJobConfig.MAP_JAVA_OPTS and 
> MRJobConfig.REDUCE_JAVA_OPTS. However, when user set a value to the 
> deprecated property "mapred.child.java.opts", hadoop won't automatically 
> update its new versions properties 
> MRJobConfig.MAP_JAVA_OPTS("mapreduce.map.java.opts") and 
> MRJobConfig.REDUCE_JAVA_OPTS("mapreduce.reduce.java.opts"). As hadoop will 
> update the new version properties for many other deprecated properties, we 
> also should support such feature on the old property 
> "mapred.child.java.opts", otherwise it might bring some imcompatible issues.



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