[
https://issues.apache.org/jira/browse/MAPREDUCE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850501#action_12850501
]
Hadoop QA commented on MAPREDUCE-1304:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12439944/MAPREDUCE-1304.3.patch
against trunk revision 928104.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/65/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/65/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/65/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/65/console
This message is automatically generated.
> Add counters for task time spent in GC
> --------------------------------------
>
> Key: MAPREDUCE-1304
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1304
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: task
> Reporter: Todd Lipcon
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-1304.2.patch, MAPREDUCE-1304.3.patch,
> MAPREDUCE-1304.patch
>
>
> It's easy to grab the number of millis spent in GC (see JvmMetrics for
> example). Exposing these as task counters would be handy - occasionally I've
> seen user jobs where long GC pauses cause big "unexplainable" performance
> problems, and a large counter would make it obvious to the user what's going
> on.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
