[
https://issues.apache.org/jira/browse/MAPREDUCE-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126347#comment-13126347
]
Hadoop QA commented on MAPREDUCE-3059:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12498851/MAPREDUCE-3059.patch
against trunk revision .
+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 (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1001//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1001//console
This message is automatically generated.
> QueueMetrics do not have metrics for aggregate containers-allocated and
> aggregate containers-released
> -----------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3059
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3059
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Karam Singh
> Assignee: Devaraj K
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-3059.patch
>
>
> QueueMetrics for ResourceManager do not have any metrics for aggregate
> containers-allocated and containers-released.
> We need the aggregates of containers-allocated and containers-released to
> figure out the rate at which RM is dishing out containers. NodeManager do
> have containers-launched and container-released metrics, but this is not
> across all nodes; so to get the cluster level aggregate, we need to
> preprocess NM metrics from all nodes - which is troublesome.
> Currently, we do have AllocatedContainers and PendingContainers which reflect
> the running containers given out to AMs, and containers waiting for
> allocation respectively.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira