[
https://issues.apache.org/jira/browse/MAPREDUCE-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated MAPREDUCE-2738:
-------------------------------------------
Fix Version/s: 0.24.0
Target Version/s: 0.23.0, 0.24.0
Affects Version/s: 0.24.0
Status: Patch Available (was: Open)
This patch adds in two new, small tables at the top of several pages on the RM.
The first table is always there and shows the stats for the cluster Total Apps
Submitted, Total Containers Running, Total Memory in the cluster, Memory used,
Memory reserved, Total NMs, Blacklisted NM, and Excluded NMs.
The NMs are links to lists of NMs in that state. The nodes page was updated to
support filtering by a given state.
Also if user level metrics are enabled in the scheduler, and web Authentication
is enabled then a second table showing stats for the current user is shown. It
includes (just for this user) Apps submitted, containers running, containers
pending, containers reserved, memory used, memory pending, memory reserved.
I did not add in a link to the jobhistory server, because that is map/reduce
specific. If this is a blocker then I will add in a new config option for yarn
which will be a list of links to various servers that display UIs related to
this and add them in of the left hand nav bar.
> 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
