You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org> on 2012/01/31 02:34:10 UTC
[jira] [Commented] (MAPREDUCE-3764) AllocatedGB etc metrics
incorrect if min-allocation-mb isn't a multiple of 1GB
[ https://issues.apache.org/jira/browse/MAPREDUCE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196623#comment-13196623 ]
Hadoop QA commented on MAPREDUCE-3764:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12512503/MAPREDUCE-3764.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 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 eclipse:eclipse. The patch built with eclipse:eclipse.
+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 failed these unit tests:
org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestQueueMetrics
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1718//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1718//console
This message is automatically generated.
> AllocatedGB etc metrics incorrect if min-allocation-mb isn't a multiple of 1GB
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3764
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3764
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Siddharth Seth
> Assignee: Arun C Murthy
> Priority: Critical
> Attachments: MAPREDUCE-3764.patch
>
>
> MutableGaugeInt incremented as {{allocatedGB.incr(res.getMemory() / GB * containers);}}
> Setting yarn.scheduler.capacity.minimum-allocation-mb to 1536 - each increment is counted as 1GB.
> Trying to analyze the metrics - looks like the cluster is never over 67-68% utilized, depending on high ram requests.
--
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