[
https://issues.apache.org/jira/browse/MAPREDUCE-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112763#comment-13112763
]
Hadoop QA commented on MAPREDUCE-3050:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12496151/MR-3050.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 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/827//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/827//console
This message is automatically generated.
> YarnScheduler needs to expose Resource Usage Information
> --------------------------------------------------------
>
> Key: MAPREDUCE-3050
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3050
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 0.23.0, 0.24.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Blocker
> Fix For: 0.23.0, 0.24.0
>
> Attachments: MR-3050.txt, MR-3050.txt
>
>
> Before the recent refactor The nodes had information in them about how much
> resources they were using. This information is not hidden inside
> SchedulerNode. Similarly resource usage information about an application, or
> in aggregate is only available through the Scheduler and there is not
> interface to pull it out.
> We need to expose APIs to get Resource and Container information from the
> scheduler, in aggregate across the entire cluster, per application, per node,
> and ideally also per queue if applicable (although there are no JIRAs I am
> aware of that need this right now).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
