[
https://issues.apache.org/jira/browse/MAPREDUCE-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120186#comment-13120186
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-2738:
----------------------------------------------------
I checked MRV1 JT. We have Blacklisted Nodes, Graylisted Nodes(which is never
used as global-blacklisting wasn't used) and Excluded Nodes. And there is no
sign of Lost nodes, which is a limitation in JT UI and can be fixed in YARN. We
can add separate columns for DECOMMISSIONED, LOST and UNHEALTHY nodes if the
number of columns isn't a problem.
> 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
