[jira] [Commented] (MAPREDUCE-4972) Coverage fixing for org.apache.hadoop.mapreduce.jobhistory
[
https://issues.apache.org/jira/browse/MAPREDUCE-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573301#comment-13573301
]
Hadoop QA commented on MAPREDUCE-4972:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12568378/MAPREDUCE-4972-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 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}. The javadoc tool did not generate any
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 1.3.9) 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-hs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3316//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3316//console
This message is automatically generated.
Coverage fixing for org.apache.hadoop.mapreduce.jobhistory
---
Key: MAPREDUCE-4972
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4972
Project: Hadoop Map/Reduce
Issue Type: Test
Components: mrv2
Reporter: Aleksey Gorshkov
Attachments: HADOOP-9092-branch-0.23-a.patch,
HADOOP-9092-branch-0.23.patch, HADOOP-9092-branch-2-a.patch,
HADOOP-9092-branch-2.patch, HADOOP-9092-trunk-a.patch,
HADOOP-9092-trunk.patch, MAPREDUCE-4972-branch-0.23.patch,
MAPREDUCE-4972-trunk.patch
Coverage fixing for package org.apache.hadoop.mapreduce.jobhistory
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4977) Documentation for pluggable shuffle and pluggable sort
[ https://issues.apache.org/jira/browse/MAPREDUCE-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573374#comment-13573374 ] Hudson commented on MAPREDUCE-4977: --- Integrated in Hadoop-Yarn-trunk #120 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/120/]) MAPREDUCE-4977. Documentation for pluggable shuffle and pluggable sort. (tucu) (Revision 1443168) Result = FAILURE tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443168 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/apt/PluggableShuffleAndPluggableSort.apt.vm * /hadoop/common/trunk/hadoop-project/src/site/site.xml Documentation for pluggable shuffle and pluggable sort -- Key: MAPREDUCE-4977 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4977 Project: Hadoop Map/Reduce Issue Type: Improvement Components: documentation Affects Versions: 2.0.3-alpha Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 2.0.3-alpha Attachments: MAPREDUCE-4877.patch, MAPREDUCE-4877.patch Add documentation with basic information on pluggable shuffle and sort. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4822) Unnecessary conversions in History Events
[
https://issues.apache.org/jira/browse/MAPREDUCE-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573376#comment-13573376
]
Hudson commented on MAPREDUCE-4822:
---
Integrated in Hadoop-Yarn-trunk #120 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/120/])
MAPREDUCE-4822. Unnecessary conversions in History Events. Contributed by
Chu Tong (Revision 1443257)
Result = FAILURE
jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443257
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/MapAttemptFinishedEvent.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/ReduceAttemptFinishedEvent.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/TaskAttemptFinishedEvent.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/TaskFinishedEvent.java
Unnecessary conversions in History Events
-
Key: MAPREDUCE-4822
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4822
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: jobhistoryserver
Affects Versions: 0.23.4
Reporter: Robert Joseph Evans
Assignee: Chu Tong
Priority: Trivial
Labels: patch
Fix For: 2.0.3-alpha, 0.23.7
Attachments: MAPREDUCE-4822.patch
There are a number of conversions in the Job History Event classes that are
totally unnecessary. It appears that they were originally used to convert
from the internal avro format, but now many of them do not pull the values
from the avro they store them internally.
For example:
{code:title=TaskAttemptFinishedEvent.java}
/** Get the task type */
public TaskType getTaskType() {
return TaskType.valueOf(taskType.toString());
}
{code}
The code currently is taking an enum, converting it to a string and then
asking the same enum to convert it back to an enum. If java work properly
this should be a noop and a reference to the original taskType should be
returned.
There are several places that a string is having toString called on it, and
since strings are immutable it returns a reference to itself.
The various ids are not immutable and probably should not be changed at this
point.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4905) test org.apache.hadoop.mapred.pipes
[ https://issues.apache.org/jira/browse/MAPREDUCE-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573381#comment-13573381 ] Hudson commented on MAPREDUCE-4905: --- Integrated in Hadoop-Yarn-trunk #120 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/120/]) MAPREDUCE-4905. test org.apache.hadoop.mapred.pipes (Aleksey Gorshkov via bobby) (Revision 1443027) Result = FAILURE bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443027 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/pipes/Submitter.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/CommonStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeApplicationRunnableStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeApplicationStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeReducerStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/TestPipeApplication.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/TestPipesNonJavaInputFormat.java test org.apache.hadoop.mapred.pipes --- Key: MAPREDUCE-4905 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4905 Project: Hadoop Map/Reduce Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Aleksey Gorshkov Assignee: Aleksey Gorshkov Fix For: 3.0.0, 2.0.3-alpha, 0.23.7 Attachments: MAPREDUCE-4905-trunk-a.patch, MAPREDUCE-4905-trunk-b.patch, MAPREDUCE-4905-trunk.patch tests for org.apache.hadoop.mapred.pipes patch MAPREDUCE-4905-trunk.patch for trunk, branch-2, branch-0.23 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4671) AM does not tell the RM about container requests that are no longer needed
[ https://issues.apache.org/jira/browse/MAPREDUCE-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573380#comment-13573380 ] Hudson commented on MAPREDUCE-4671: --- Integrated in Hadoop-Yarn-trunk #120 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/120/]) MAPREDUCE-4671. AM does not tell the RM about container requests which are no longer needed. Contributed by Bikas Saha. (Revision 1443323) Result = FAILURE sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443323 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerRequestor.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestRMContainerAllocator.java AM does not tell the RM about container requests that are no longer needed -- Key: MAPREDUCE-4671 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4671 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.3, 2.0.0-alpha Reporter: Bikas Saha Assignee: Bikas Saha Fix For: 2.0.4-beta Attachments: MAPREDUCE-4671.1.patch, MAPREDUCE-4671.2.patch, MAPREDUCE-4671.3.patch, MAPREDUCE-4671.4.patch, MAPREDUCE-4671.txt Say the AM wanted a container at hosts h1, h2, h3. After getting a container at h1 it should tell RM that it no longer needs containers at h2, h3. Otherwise on the RM h2, h3 remain valid allocation locations. The AM RMContainerAllocator does remove these resource requests internally. When the resource request container count drops to 0 then it drops the resource request from its tables but forgets to send the 0 sized request to the RM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4637) Killing an unassigned task attempt causes the job to fail
[ https://issues.apache.org/jira/browse/MAPREDUCE-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573429#comment-13573429 ] Hudson commented on MAPREDUCE-4637: --- Integrated in Hadoop-Hdfs-0.23-Build #518 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/518/]) MAPREDUCE-4637. Handle TaskAttempt diagnostic updates while in the NEW and UNASSIGNED states. (Mayank Bansal via tgraves) (Revision 1443243) Result = SUCCESS tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443243 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/job/impl/TaskAttemptImpl.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/job/impl/TestTaskAttempt.java Killing an unassigned task attempt causes the job to fail - Key: MAPREDUCE-4637 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4637 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 2.0.0-alpha Reporter: Tom White Assignee: Mayank Bansal Fix For: 2.0.3-alpha, 0.23.7 Attachments: MAPREDUCE-4637-trunk.patch, MAPREDUCE-4637-trunk-v2.patch, MAPREDUCE-4637-trunk-v3.patch, MAPREDUCE-4637-trunk-v4.patch, MAPREDUCE-4637-trunk-v5.patch, MAPREDUCE-4637-trunk-v6.patch, MapReduce.png Attempting to kill a task attempt that has been scheduled but is not running causes an invalid state transition and the AM to stop with an error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4905) test org.apache.hadoop.mapred.pipes
[ https://issues.apache.org/jira/browse/MAPREDUCE-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573434#comment-13573434 ] Hudson commented on MAPREDUCE-4905: --- Integrated in Hadoop-Hdfs-0.23-Build #518 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/518/]) svn merge -c 1443027. FIXES: MAPREDUCE-4905. test org.apache.hadoop.mapred.pipes (Aleksey Gorshkov via bobby) (Revision 1443036) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443036 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/pipes/Submitter.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/CommonStub.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeApplicationRunnableStub.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeApplicationStub.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeReducerStub.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/TestPipeApplication.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/TestPipesNonJavaInputFormat.java test org.apache.hadoop.mapred.pipes --- Key: MAPREDUCE-4905 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4905 Project: Hadoop Map/Reduce Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Aleksey Gorshkov Assignee: Aleksey Gorshkov Fix For: 3.0.0, 2.0.3-alpha, 0.23.7 Attachments: MAPREDUCE-4905-trunk-a.patch, MAPREDUCE-4905-trunk-b.patch, MAPREDUCE-4905-trunk.patch tests for org.apache.hadoop.mapred.pipes patch MAPREDUCE-4905-trunk.patch for trunk, branch-2, branch-0.23 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4822) Unnecessary conversions in History Events
[
https://issues.apache.org/jira/browse/MAPREDUCE-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573432#comment-13573432
]
Hudson commented on MAPREDUCE-4822:
---
Integrated in Hadoop-Hdfs-0.23-Build #518 (See
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/518/])
svn merge -c 1443257 FIXES: MAPREDUCE-4822. Unnecessary conversions in
History Events. Contributed by Chu Tong (Revision 1443271)
Result = SUCCESS
jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443271
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/MapAttemptFinishedEvent.java
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/ReduceAttemptFinishedEvent.java
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/TaskAttemptFinishedEvent.java
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/TaskFinishedEvent.java
Unnecessary conversions in History Events
-
Key: MAPREDUCE-4822
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4822
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: jobhistoryserver
Affects Versions: 0.23.4
Reporter: Robert Joseph Evans
Assignee: Chu Tong
Priority: Trivial
Labels: patch
Fix For: 2.0.3-alpha, 0.23.7
Attachments: MAPREDUCE-4822.patch
There are a number of conversions in the Job History Event classes that are
totally unnecessary. It appears that they were originally used to convert
from the internal avro format, but now many of them do not pull the values
from the avro they store them internally.
For example:
{code:title=TaskAttemptFinishedEvent.java}
/** Get the task type */
public TaskType getTaskType() {
return TaskType.valueOf(taskType.toString());
}
{code}
The code currently is taking an enum, converting it to a string and then
asking the same enum to convert it back to an enum. If java work properly
this should be a noop and a reference to the original taskType should be
returned.
There are several places that a string is having toString called on it, and
since strings are immutable it returns a reference to itself.
The various ids are not immutable and probably should not be changed at this
point.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4977) Documentation for pluggable shuffle and pluggable sort
[ https://issues.apache.org/jira/browse/MAPREDUCE-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573450#comment-13573450 ] Hudson commented on MAPREDUCE-4977: --- Integrated in Hadoop-Hdfs-trunk #1309 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1309/]) MAPREDUCE-4977. Documentation for pluggable shuffle and pluggable sort. (tucu) (Revision 1443168) Result = FAILURE tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443168 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/apt/PluggableShuffleAndPluggableSort.apt.vm * /hadoop/common/trunk/hadoop-project/src/site/site.xml Documentation for pluggable shuffle and pluggable sort -- Key: MAPREDUCE-4977 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4977 Project: Hadoop Map/Reduce Issue Type: Improvement Components: documentation Affects Versions: 2.0.3-alpha Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 2.0.3-alpha Attachments: MAPREDUCE-4877.patch, MAPREDUCE-4877.patch Add documentation with basic information on pluggable shuffle and sort. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4822) Unnecessary conversions in History Events
[
https://issues.apache.org/jira/browse/MAPREDUCE-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573452#comment-13573452
]
Hudson commented on MAPREDUCE-4822:
---
Integrated in Hadoop-Hdfs-trunk #1309 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1309/])
MAPREDUCE-4822. Unnecessary conversions in History Events. Contributed by
Chu Tong (Revision 1443257)
Result = FAILURE
jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443257
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/MapAttemptFinishedEvent.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/ReduceAttemptFinishedEvent.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/TaskAttemptFinishedEvent.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/TaskFinishedEvent.java
Unnecessary conversions in History Events
-
Key: MAPREDUCE-4822
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4822
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: jobhistoryserver
Affects Versions: 0.23.4
Reporter: Robert Joseph Evans
Assignee: Chu Tong
Priority: Trivial
Labels: patch
Fix For: 2.0.3-alpha, 0.23.7
Attachments: MAPREDUCE-4822.patch
There are a number of conversions in the Job History Event classes that are
totally unnecessary. It appears that they were originally used to convert
from the internal avro format, but now many of them do not pull the values
from the avro they store them internally.
For example:
{code:title=TaskAttemptFinishedEvent.java}
/** Get the task type */
public TaskType getTaskType() {
return TaskType.valueOf(taskType.toString());
}
{code}
The code currently is taking an enum, converting it to a string and then
asking the same enum to convert it back to an enum. If java work properly
this should be a noop and a reference to the original taskType should be
returned.
There are several places that a string is having toString called on it, and
since strings are immutable it returns a reference to itself.
The various ids are not immutable and probably should not be changed at this
point.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4671) AM does not tell the RM about container requests that are no longer needed
[ https://issues.apache.org/jira/browse/MAPREDUCE-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573456#comment-13573456 ] Hudson commented on MAPREDUCE-4671: --- Integrated in Hadoop-Hdfs-trunk #1309 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1309/]) MAPREDUCE-4671. AM does not tell the RM about container requests which are no longer needed. Contributed by Bikas Saha. (Revision 1443323) Result = FAILURE sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443323 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerRequestor.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestRMContainerAllocator.java AM does not tell the RM about container requests that are no longer needed -- Key: MAPREDUCE-4671 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4671 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.3, 2.0.0-alpha Reporter: Bikas Saha Assignee: Bikas Saha Fix For: 2.0.4-beta Attachments: MAPREDUCE-4671.1.patch, MAPREDUCE-4671.2.patch, MAPREDUCE-4671.3.patch, MAPREDUCE-4671.4.patch, MAPREDUCE-4671.txt Say the AM wanted a container at hosts h1, h2, h3. After getting a container at h1 it should tell RM that it no longer needs containers at h2, h3. Otherwise on the RM h2, h3 remain valid allocation locations. The AM RMContainerAllocator does remove these resource requests internally. When the resource request container count drops to 0 then it drops the resource request from its tables but forgets to send the 0 sized request to the RM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4905) test org.apache.hadoop.mapred.pipes
[ https://issues.apache.org/jira/browse/MAPREDUCE-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573457#comment-13573457 ] Hudson commented on MAPREDUCE-4905: --- Integrated in Hadoop-Hdfs-trunk #1309 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1309/]) MAPREDUCE-4905. test org.apache.hadoop.mapred.pipes (Aleksey Gorshkov via bobby) (Revision 1443027) Result = FAILURE bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443027 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/pipes/Submitter.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/CommonStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeApplicationRunnableStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeApplicationStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeReducerStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/TestPipeApplication.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/TestPipesNonJavaInputFormat.java test org.apache.hadoop.mapred.pipes --- Key: MAPREDUCE-4905 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4905 Project: Hadoop Map/Reduce Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Aleksey Gorshkov Assignee: Aleksey Gorshkov Fix For: 3.0.0, 2.0.3-alpha, 0.23.7 Attachments: MAPREDUCE-4905-trunk-a.patch, MAPREDUCE-4905-trunk-b.patch, MAPREDUCE-4905-trunk.patch tests for org.apache.hadoop.mapred.pipes patch MAPREDUCE-4905-trunk.patch for trunk, branch-2, branch-0.23 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4977) Documentation for pluggable shuffle and pluggable sort
[ https://issues.apache.org/jira/browse/MAPREDUCE-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573502#comment-13573502 ] Hudson commented on MAPREDUCE-4977: --- Integrated in Hadoop-Mapreduce-trunk #1337 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1337/]) MAPREDUCE-4977. Documentation for pluggable shuffle and pluggable sort. (tucu) (Revision 1443168) Result = SUCCESS tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443168 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/apt/PluggableShuffleAndPluggableSort.apt.vm * /hadoop/common/trunk/hadoop-project/src/site/site.xml Documentation for pluggable shuffle and pluggable sort -- Key: MAPREDUCE-4977 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4977 Project: Hadoop Map/Reduce Issue Type: Improvement Components: documentation Affects Versions: 2.0.3-alpha Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 2.0.3-alpha Attachments: MAPREDUCE-4877.patch, MAPREDUCE-4877.patch Add documentation with basic information on pluggable shuffle and sort. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4822) Unnecessary conversions in History Events
[
https://issues.apache.org/jira/browse/MAPREDUCE-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573504#comment-13573504
]
Hudson commented on MAPREDUCE-4822:
---
Integrated in Hadoop-Mapreduce-trunk #1337 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1337/])
MAPREDUCE-4822. Unnecessary conversions in History Events. Contributed by
Chu Tong (Revision 1443257)
Result = SUCCESS
jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443257
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/MapAttemptFinishedEvent.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/ReduceAttemptFinishedEvent.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/TaskAttemptFinishedEvent.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/jobhistory/TaskFinishedEvent.java
Unnecessary conversions in History Events
-
Key: MAPREDUCE-4822
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4822
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: jobhistoryserver
Affects Versions: 0.23.4
Reporter: Robert Joseph Evans
Assignee: Chu Tong
Priority: Trivial
Labels: patch
Fix For: 2.0.3-alpha, 0.23.7
Attachments: MAPREDUCE-4822.patch
There are a number of conversions in the Job History Event classes that are
totally unnecessary. It appears that they were originally used to convert
from the internal avro format, but now many of them do not pull the values
from the avro they store them internally.
For example:
{code:title=TaskAttemptFinishedEvent.java}
/** Get the task type */
public TaskType getTaskType() {
return TaskType.valueOf(taskType.toString());
}
{code}
The code currently is taking an enum, converting it to a string and then
asking the same enum to convert it back to an enum. If java work properly
this should be a noop and a reference to the original taskType should be
returned.
There are several places that a string is having toString called on it, and
since strings are immutable it returns a reference to itself.
The various ids are not immutable and probably should not be changed at this
point.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4671) AM does not tell the RM about container requests that are no longer needed
[ https://issues.apache.org/jira/browse/MAPREDUCE-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573508#comment-13573508 ] Hudson commented on MAPREDUCE-4671: --- Integrated in Hadoop-Mapreduce-trunk #1337 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1337/]) MAPREDUCE-4671. AM does not tell the RM about container requests which are no longer needed. Contributed by Bikas Saha. (Revision 1443323) Result = SUCCESS sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443323 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerRequestor.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestRMContainerAllocator.java AM does not tell the RM about container requests that are no longer needed -- Key: MAPREDUCE-4671 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4671 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.3, 2.0.0-alpha Reporter: Bikas Saha Assignee: Bikas Saha Fix For: 2.0.4-beta Attachments: MAPREDUCE-4671.1.patch, MAPREDUCE-4671.2.patch, MAPREDUCE-4671.3.patch, MAPREDUCE-4671.4.patch, MAPREDUCE-4671.txt Say the AM wanted a container at hosts h1, h2, h3. After getting a container at h1 it should tell RM that it no longer needs containers at h2, h3. Otherwise on the RM h2, h3 remain valid allocation locations. The AM RMContainerAllocator does remove these resource requests internally. When the resource request container count drops to 0 then it drops the resource request from its tables but forgets to send the 0 sized request to the RM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4905) test org.apache.hadoop.mapred.pipes
[ https://issues.apache.org/jira/browse/MAPREDUCE-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573509#comment-13573509 ] Hudson commented on MAPREDUCE-4905: --- Integrated in Hadoop-Mapreduce-trunk #1337 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1337/]) MAPREDUCE-4905. test org.apache.hadoop.mapred.pipes (Aleksey Gorshkov via bobby) (Revision 1443027) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1443027 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/pipes/Submitter.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/CommonStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeApplicationRunnableStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeApplicationStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/PipeReducerStub.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/TestPipeApplication.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/pipes/TestPipesNonJavaInputFormat.java test org.apache.hadoop.mapred.pipes --- Key: MAPREDUCE-4905 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4905 Project: Hadoop Map/Reduce Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Aleksey Gorshkov Assignee: Aleksey Gorshkov Fix For: 3.0.0, 2.0.3-alpha, 0.23.7 Attachments: MAPREDUCE-4905-trunk-a.patch, MAPREDUCE-4905-trunk-b.patch, MAPREDUCE-4905-trunk.patch tests for org.apache.hadoop.mapred.pipes patch MAPREDUCE-4905-trunk.patch for trunk, branch-2, branch-0.23 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4987) TestMRJobs#testDistributedCache fails on Windows due to unexpected behavior of symlinks
[
https://issues.apache.org/jira/browse/MAPREDUCE-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573742#comment-13573742
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-4987:
But symlinks CAN be used for functional purposes i.e linking to libraries etc.
? If so we can just do the platform check in the test-case.
TestMRJobs#testDistributedCache fails on Windows due to unexpected behavior
of symlinks
---
Key: MAPREDUCE-4987
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4987
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: distributed-cache, nodemanager
Affects Versions: trunk-win
Reporter: Chris Nauroth
On Windows, {{TestMRJobs#testDistributedCache}} fails on an assertion while
checking the length of a symlink. It expects to see the length of the target
of the symlink, but Java 6 on Windows always reports that a symlink has
length 0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-4988) ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4.
Amir Sanjar created MAPREDUCE-4988: -- Summary: ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4. Key: MAPREDUCE-4988 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4988 Project: Hadoop Map/Reduce Issue Type: Bug Components: test Affects Versions: 1.1.1, 1.1.2 Environment: Linux on PPC and x86 Reporter: Amir Sanjar Fix For: 1.1.2 TestJobTrackerRestartWithCS, TestCapacitySchedulerServlet, and TestCapacitySchedulerWithJobTracker testcases potentially could fail when they are build with ant 1.8.4. Solution: port above testcases and ClusterWithCapacityScheduler class from Junit3 to Junit4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4988) ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amir Sanjar updated MAPREDUCE-4988: --- Attachment: MAPREDUCE-4988-1.1.1.patch fix for hadoop 1.1.1.. working on porting the patch to branch1 and trunck ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4. Key: MAPREDUCE-4988 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4988 Project: Hadoop Map/Reduce Issue Type: Bug Components: test Affects Versions: 1.1.1, 1.1.2 Environment: Linux on PPC and x86 Reporter: Amir Sanjar Fix For: 1.1.2 Attachments: MAPREDUCE-4988-1.1.1.patch TestJobTrackerRestartWithCS, TestCapacitySchedulerServlet, and TestCapacitySchedulerWithJobTracker testcases potentially could fail when they are build with ant 1.8.4. Solution: port above testcases and ClusterWithCapacityScheduler class from Junit3 to Junit4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4988) ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573775#comment-13573775 ] Amir Sanjar commented on MAPREDUCE-4988: looks like it has already been fixed in branch1 :) ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4. Key: MAPREDUCE-4988 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4988 Project: Hadoop Map/Reduce Issue Type: Bug Components: test Affects Versions: 1.1.1, 1.1.2 Environment: Linux on PPC and x86 Reporter: Amir Sanjar Fix For: 1.1.2 Attachments: MAPREDUCE-4988-1.1.1.patch TestJobTrackerRestartWithCS, TestCapacitySchedulerServlet, and TestCapacitySchedulerWithJobTracker testcases potentially could fail when they are build with ant 1.8.4. Solution: port above testcases and ClusterWithCapacityScheduler class from Junit3 to Junit4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4988) ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amir Sanjar updated MAPREDUCE-4988: --- Priority: Trivial (was: Major) ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4. Key: MAPREDUCE-4988 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4988 Project: Hadoop Map/Reduce Issue Type: Bug Components: test Affects Versions: 1.1.1, 1.1.2 Environment: Linux on PPC and x86 Reporter: Amir Sanjar Priority: Trivial Fix For: 1.1.2 TestJobTrackerRestartWithCS, TestCapacitySchedulerServlet, and TestCapacitySchedulerWithJobTracker testcases potentially could fail when they are build with ant 1.8.4. Solution: port above testcases and ClusterWithCapacityScheduler class from Junit3 to Junit4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4988) ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amir Sanjar updated MAPREDUCE-4988: --- Attachment: (was: MAPREDUCE-4988-1.1.1.patch) ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4. Key: MAPREDUCE-4988 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4988 Project: Hadoop Map/Reduce Issue Type: Bug Components: test Affects Versions: 1.1.1, 1.1.2 Environment: Linux on PPC and x86 Reporter: Amir Sanjar Priority: Trivial Fix For: 1.1.2 TestJobTrackerRestartWithCS, TestCapacitySchedulerServlet, and TestCapacitySchedulerWithJobTracker testcases potentially could fail when they are build with ant 1.8.4. Solution: port above testcases and ClusterWithCapacityScheduler class from Junit3 to Junit4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4988) ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amir Sanjar updated MAPREDUCE-4988: --- Attachment: MAPREDUCE-4988-1.1.1.patch for hadoop 1.1.1 only.. fix is already in branch1 ClusterWithCapacityScheduler and related testcases needs to be ported to JUnit4. Key: MAPREDUCE-4988 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4988 Project: Hadoop Map/Reduce Issue Type: Bug Components: test Affects Versions: 1.1.1, 1.1.2 Environment: Linux on PPC and x86 Reporter: Amir Sanjar Priority: Trivial Fix For: 1.1.2 Attachments: MAPREDUCE-4988-1.1.1.patch TestJobTrackerRestartWithCS, TestCapacitySchedulerServlet, and TestCapacitySchedulerWithJobTracker testcases potentially could fail when they are build with ant 1.8.4. Solution: port above testcases and ClusterWithCapacityScheduler class from Junit3 to Junit4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-4989) JSONify DataTables input data for Attempts page
Ravi Prakash created MAPREDUCE-4989: --- Summary: JSONify DataTables input data for Attempts page Key: MAPREDUCE-4989 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4989 Project: Hadoop Map/Reduce Issue Type: Improvement Components: jobhistoryserver, mr-am Affects Versions: 0.23.6 Reporter: Ravi Prakash Assignee: Ravi Prakash Use deferred rendering for the attempts page as was done in MAPREDUCE-4720. I'm sorry I didn't realize earlier that this table could be huge too. Thanks to [~jlowe] for pointing it out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4989) JSONify DataTables input data for Attempts page
[ https://issues.apache.org/jira/browse/MAPREDUCE-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated MAPREDUCE-4989: Attachment: MAPREDUCE-4989.patch The patch for trunk JSONify DataTables input data for Attempts page --- Key: MAPREDUCE-4989 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4989 Project: Hadoop Map/Reduce Issue Type: Improvement Components: jobhistoryserver, mr-am Affects Versions: 0.23.6 Reporter: Ravi Prakash Assignee: Ravi Prakash Attachments: MAPREDUCE-4989.patch Use deferred rendering for the attempts page as was done in MAPREDUCE-4720. I'm sorry I didn't realize earlier that this table could be huge too. Thanks to [~jlowe] for pointing it out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4989) JSONify DataTables input data for Attempts page
[ https://issues.apache.org/jira/browse/MAPREDUCE-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated MAPREDUCE-4989: Status: Patch Available (was: Open) JSONify DataTables input data for Attempts page --- Key: MAPREDUCE-4989 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4989 Project: Hadoop Map/Reduce Issue Type: Improvement Components: jobhistoryserver, mr-am Affects Versions: 0.23.6 Reporter: Ravi Prakash Assignee: Ravi Prakash Attachments: MAPREDUCE-4989.branch-0.23.patch, MAPREDUCE-4989.patch Use deferred rendering for the attempts page as was done in MAPREDUCE-4720. I'm sorry I didn't realize earlier that this table could be huge too. Thanks to [~jlowe] for pointing it out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4989) JSONify DataTables input data for Attempts page
[ https://issues.apache.org/jira/browse/MAPREDUCE-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated MAPREDUCE-4989: Attachment: MAPREDUCE-4989.branch-0.23.patch The patch for branch-0.23 JSONify DataTables input data for Attempts page --- Key: MAPREDUCE-4989 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4989 Project: Hadoop Map/Reduce Issue Type: Improvement Components: jobhistoryserver, mr-am Affects Versions: 0.23.6 Reporter: Ravi Prakash Assignee: Ravi Prakash Attachments: MAPREDUCE-4989.branch-0.23.patch, MAPREDUCE-4989.patch Use deferred rendering for the attempts page as was done in MAPREDUCE-4720. I'm sorry I didn't realize earlier that this table could be huge too. Thanks to [~jlowe] for pointing it out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4989) JSONify DataTables input data for Attempts page
[
https://issues.apache.org/jira/browse/MAPREDUCE-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574090#comment-13574090
]
Hadoop QA commented on MAPREDUCE-4989:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12568497/MAPREDUCE-4989.branch-0.23.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3317//console
This message is automatically generated.
JSONify DataTables input data for Attempts page
---
Key: MAPREDUCE-4989
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4989
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: jobhistoryserver, mr-am
Affects Versions: 0.23.6
Reporter: Ravi Prakash
Assignee: Ravi Prakash
Attachments: MAPREDUCE-4989.branch-0.23.patch, MAPREDUCE-4989.patch
Use deferred rendering for the attempts page as was done in MAPREDUCE-4720.
I'm sorry I didn't realize earlier that this table could be huge too. Thanks
to [~jlowe] for pointing it out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4987) TestMRJobs#testDistributedCache fails on Windows due to unexpected behavior of symlinks
[
https://issues.apache.org/jira/browse/MAPREDUCE-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574097#comment-13574097
]
Ivan Mitic commented on MAPREDUCE-4987:
---
Thanks for reporting this Chris.
bq. But symlinks CAN be used for functional purposes i.e linking to libraries
etc. ?
Hi Vinod. I believe we'll have to port the branch-1-win semantic to trunk to
properly support symlinks on both Java6 and Java7 on Windows. Yes, symlinks can
be created to point to folders and files, however, Java6 does not interpret
them correctly. We've seen so many issues with symlinks on Java6, and the only
option that worked fine (and was signed off on) is to do a file copy in case of
Java6. HADOOP-9061 talks about some of these problems.
bq. If so we can just do the platform check in the test-case.
We also initially thought this would be fine (you can check thru branch-1-win
history :)). However, the real problem comes when someone tries to access the
symlink thru Java APIs. Examples of problems are, File#length on symlinks
returns zero. This means that RLFS does not work on top of symlinks.
Additionally, File#renameTo on symlink renames the target file instead of the
symlink (really strange I know :)).
Hope this helps
TestMRJobs#testDistributedCache fails on Windows due to unexpected behavior
of symlinks
---
Key: MAPREDUCE-4987
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4987
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: distributed-cache, nodemanager
Affects Versions: trunk-win
Reporter: Chris Nauroth
On Windows, {{TestMRJobs#testDistributedCache}} fails on an assertion while
checking the length of a symlink. It expects to see the length of the target
of the symlink, but Java 6 on Windows always reports that a symlink has
length 0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4989) JSONify DataTables input data for Attempts page
[ https://issues.apache.org/jira/browse/MAPREDUCE-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated MAPREDUCE-4989: Attachment: MAPREDUCE-4989.patch Re-uploading the SAME patch for trunk because Hadoop QA is silly. :D JSONify DataTables input data for Attempts page --- Key: MAPREDUCE-4989 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4989 Project: Hadoop Map/Reduce Issue Type: Improvement Components: jobhistoryserver, mr-am Affects Versions: 0.23.6 Reporter: Ravi Prakash Assignee: Ravi Prakash Attachments: MAPREDUCE-4989.branch-0.23.patch, MAPREDUCE-4989.patch, MAPREDUCE-4989.patch Use deferred rendering for the attempts page as was done in MAPREDUCE-4720. I'm sorry I didn't realize earlier that this table could be huge too. Thanks to [~jlowe] for pointing it out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4989) JSONify DataTables input data for Attempts page
[
https://issues.apache.org/jira/browse/MAPREDUCE-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574116#comment-13574116
]
Hadoop QA commented on MAPREDUCE-4989:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12568499/MAPREDUCE-4989.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
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 1.3.9) 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-hs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3318//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3318//console
This message is automatically generated.
JSONify DataTables input data for Attempts page
---
Key: MAPREDUCE-4989
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4989
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: jobhistoryserver, mr-am
Affects Versions: 0.23.6
Reporter: Ravi Prakash
Assignee: Ravi Prakash
Attachments: MAPREDUCE-4989.branch-0.23.patch, MAPREDUCE-4989.patch,
MAPREDUCE-4989.patch
Use deferred rendering for the attempts page as was done in MAPREDUCE-4720.
I'm sorry I didn't realize earlier that this table could be huge too. Thanks
to [~jlowe] for pointing it out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4643) Make job-history cleanup-period configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated MAPREDUCE-4643: -- Attachment: MAPREDUCE-4643-branch-1-5.patch Make job-history cleanup-period configurable Key: MAPREDUCE-4643 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4643 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver Affects Versions: 1.0.3 Reporter: Karthik Kambatla Assignee: Sandy Ryza Attachments: MAPREDUCE-4643-branch1-2.patch, MAPREDUCE-4643-branch-1-3.patch, MAPREDUCE-4643-branch-1-4.patch, MAPREDUCE-4643-branch-1-5.patch, MAPREDUCE-4643-branch1.patch, MAPREDUCE-4643-branch1.patch, MAPREDUCE-4643.patch Job history cleanup should be made configurable. Currently, it is set to 1 month by default. The DEBUG_MODE (to be removed, see MAPREDUCE-4629) sets it to 20 minutes, but it should be configurable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4643) Make job-history cleanup-period configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574156#comment-13574156 ] Sandy Ryza commented on MAPREDUCE-4643: --- Latest patch adds test that runs in less than a second. Make job-history cleanup-period configurable Key: MAPREDUCE-4643 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4643 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver Affects Versions: 1.0.3 Reporter: Karthik Kambatla Assignee: Sandy Ryza Attachments: MAPREDUCE-4643-branch1-2.patch, MAPREDUCE-4643-branch-1-3.patch, MAPREDUCE-4643-branch-1-4.patch, MAPREDUCE-4643-branch-1-5.patch, MAPREDUCE-4643-branch1.patch, MAPREDUCE-4643-branch1.patch, MAPREDUCE-4643.patch Job history cleanup should be made configurable. Currently, it is set to 1 month by default. The DEBUG_MODE (to be removed, see MAPREDUCE-4629) sets it to 20 minutes, but it should be configurable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4643) Make job-history cleanup-period configurable
[
https://issues.apache.org/jira/browse/MAPREDUCE-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574164#comment-13574164
]
Hadoop QA commented on MAPREDUCE-4643:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12568512/MAPREDUCE-4643-branch-1-5.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3319//console
This message is automatically generated.
Make job-history cleanup-period configurable
Key: MAPREDUCE-4643
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4643
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: jobhistoryserver
Affects Versions: 1.0.3
Reporter: Karthik Kambatla
Assignee: Sandy Ryza
Attachments: MAPREDUCE-4643-branch1-2.patch,
MAPREDUCE-4643-branch-1-3.patch, MAPREDUCE-4643-branch-1-4.patch,
MAPREDUCE-4643-branch-1-5.patch, MAPREDUCE-4643-branch1.patch,
MAPREDUCE-4643-branch1.patch, MAPREDUCE-4643.patch
Job history cleanup should be made configurable. Currently, it is set to 1
month by default. The DEBUG_MODE (to be removed, see MAPREDUCE-4629) sets it
to 20 minutes, but it should be configurable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4643) Make job-history cleanup-period configurable
[
https://issues.apache.org/jira/browse/MAPREDUCE-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574167#comment-13574167
]
Karthik Kambatla commented on MAPREDUCE-4643:
-
Cool test, Sandy. The latest patch looks mostly good; minor comments:
# We should rename {{run(long now)}} to {{runCleaner(long now)}} to avoid
confusion.
# The test doesn't seem to test the case where only some of the files within a
directory need to be deleted. To add this case to the test, we might have to
calculate the paths etc. instead of hardcoding them.
Make job-history cleanup-period configurable
Key: MAPREDUCE-4643
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4643
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: jobhistoryserver
Affects Versions: 1.0.3
Reporter: Karthik Kambatla
Assignee: Sandy Ryza
Attachments: MAPREDUCE-4643-branch1-2.patch,
MAPREDUCE-4643-branch-1-3.patch, MAPREDUCE-4643-branch-1-4.patch,
MAPREDUCE-4643-branch-1-5.patch, MAPREDUCE-4643-branch1.patch,
MAPREDUCE-4643-branch1.patch, MAPREDUCE-4643.patch
Job history cleanup should be made configurable. Currently, it is set to 1
month by default. The DEBUG_MODE (to be removed, see MAPREDUCE-4629) sets it
to 20 minutes, but it should be configurable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4931) Add user-APIs for classpath precedence control
[
https://issues.apache.org/jira/browse/MAPREDUCE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574186#comment-13574186
]
Karthik Kambatla commented on MAPREDUCE-4931:
-
[~ste...@apache.org], makes sense to start that discussion soon, now that
discussions of a beta release in the near-future have come up. :)
Add user-APIs for classpath precedence control
--
Key: MAPREDUCE-4931
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4931
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: client
Affects Versions: 1.0.0
Reporter: Harsh J
Priority: Minor
The feature config from MAPREDUCE-1938 of allowing tasks to start with
user-classes-first is fairly popular and can use its own API hooks in
Job/JobConf classes, making it easier to discover and use it rather than
continuing to keep it as an advanced param.
I propose to add two APIs to Job/JobConf:
{code}
void setUserClassesTakesPrecedence(boolean)
boolean userClassesTakesPrecedence()
{code}
Both of which, depending on their branch of commit, set the property
{{mapreduce.user.classpath.first}} (1.x) or
{{mapreduce.job.user.classpath.first}} (trunk, 2.x and if needed, in 0.23.x).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2354) Shuffle should be optimized
[ https://issues.apache.org/jira/browse/MAPREDUCE-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574292#comment-13574292 ] Karthik Kambatla commented on MAPREDUCE-2354: - [~wangmeng], could you give us any updates on this? Shuffle should be optimized --- Key: MAPREDUCE-2354 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2354 Project: Hadoop Map/Reduce Issue Type: Improvement Components: task, tasktracker Affects Versions: 0.20.1 Reporter: MengWang Labels: mapreduce, shuffle Fix For: 0.24.0 Our study shows that shuffle is a performance bottleneck of mapreduce computing. There are some problems of shuffle: (1)Shuffle and reduce are tightly-coupled, usually shuffle phase doesn't consume too much memory and CPU, so theoretically, reducetasks's slot can be used for other computing tasks when copying data from maps. This method will enhance cluster utilization. Furthermore, should shuffle be separated from reduce? Then shuffle will not use reduce's slot,we need't distinguish between map slots and reduce slots at all. (2)For large jobs, shuffle will use too many network connections, Data transmitted by each network connection is very little, which is inefficient. From 0.21.0 one connection can transfer several map outputs, but i think this is not enough. Maybe we can use a per node shuffle client progress(like tasktracker) to shuffle data for all reduce tasks on this node, then we can shuffle more data trough one connection. (3)Too many concurrent connections will cause shuffle server do massive random IO, which is inefficient. Maybe we can aggregate http request(like delay scheduler), then random IO will be sequential. (4)How to manage memory used by shuffle efficiently. We use buddy memory allocation, which will waste a considerable amount of memory. (5)If shuffle separated from reduce, then we must figure out how to do reduce locality? (6)Can we store map outputs in a Storage system(like hdfs)? (7)Can shuffle be a general data transfer service, which not only for map/reduce paradigm? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4990) Construct debug strings conditionally in ShuffleHandler.Shuffle#sendMapOutput()
[
https://issues.apache.org/jira/browse/MAPREDUCE-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla updated MAPREDUCE-4990:
Issue Type: Improvement (was: Bug)
Construct debug strings conditionally in
ShuffleHandler.Shuffle#sendMapOutput()
---
Key: MAPREDUCE-4990
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4990
Project: Hadoop Map/Reduce
Issue Type: Improvement
Affects Versions: 2.0.3-alpha, 0.23.5
Reporter: Karthik Kambatla
Assignee: Karthik Kambatla
Priority: Trivial
In {{#sendMapOutput()}}, the debug statements are not wrapped in the
customary {{#isDebugEnabled()}} condition. Given this piece of code is
critical for performance, it would be nice to fix it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-4990) Construct debug strings conditionally in ShuffleHandler.Shuffle#sendMapOutput()
Karthik Kambatla created MAPREDUCE-4990:
---
Summary: Construct debug strings conditionally in
ShuffleHandler.Shuffle#sendMapOutput()
Key: MAPREDUCE-4990
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4990
Project: Hadoop Map/Reduce
Issue Type: Bug
Affects Versions: 0.23.5, 2.0.3-alpha
Reporter: Karthik Kambatla
Assignee: Karthik Kambatla
Priority: Trivial
In {{#sendMapOutput()}}, the debug statements are not wrapped in the customary
{{#isDebugEnabled()}} condition. Given this piece of code is critical for
performance, it would be nice to fix it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
