[jira] [Commented] (MAPREDUCE-2738) Missing cluster level stats on the RM UI

["Hadoop QA (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119355#comment-13119355 ] 

Hadoop QA commented on MAPREDUCE-2738:
--------------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12497469/MR-2738.txt
  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 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/927//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/927//console

This message is automatically generated.
                
> Missing cluster level stats on the RM UI
> ----------------------------------------
>
>                 Key: MAPREDUCE-2738
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2738
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Ramya Sunil
>            Assignee: Robert Joseph Evans
>            Priority: Blocker
>             Fix For: 0.23.0, 0.24.0
>
>         Attachments: MR-2738.txt
>
>
> Cluster usage information such as the following are currently not available in the RM UI. 
> - Total number of apps submitted so far
> - Total number of containers running/total memory usage 
> - Total capacity of the cluster (in terms of memory)
> - Reserved memory
> - Total number of NMs - sorting based on Node IDs is an option but when there are lost NMs or restarted NMs, the node ids does not correspond to the actual value
> - Blacklisted NMs - sorting based on health-status and counting manually is not very straight forward
> - Excluded NMs
> - Handle to the jobhistory server

--
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