[
https://issues.apache.org/jira/browse/MAPREDUCE-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108804#comment-13108804
]
Robert Joseph Evans commented on MAPREDUCE-2738:
------------------------------------------------
I have been looking at this and I don't like using JMX. Partly because the
fifo scheduler does not update JMX correctly, which I can fix, but also because
the queue name must be included in the JMX name to get the info back correctly.
Because of this there is no guarantee that a scheduler will have a root queue,
or something like that, so it because very difficult to write something generic
with JMX that can cover all cases.
Instead I would like to add in some APIs to YarnScheduler to get back the
information we want. It may get the information from metrics if it feels like
it. This is also very similar to what MAPREDUCE-2789 appears to need, but on a
per application basis instead of on an aggregate basis for the entire cluster.
Also we could add in some APIs on a per node basis so the node manager GUI can
get back to where it was before and display resources used, reserved, etc. I
will talk with the owner of MAPREDUCE-2789 about potentially filing a separate
JIRA to do this work on.
> 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
> Reporter: Ramya Sunil
> Assignee: Robert Joseph Evans
> Priority: Blocker
> Fix For: 0.23.0
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
