hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2738) Missing cluster level stats on the RM UI
Date Tue, 04 Oct 2011 14:30:34 GMT

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

Vinod Kumar Vavilapalli commented on MAPREDUCE-2738:

Gone through the patch. Looks mostly good!

Some suggestions for mostly cosmetic changes:
 - I'd prefer 'good' and 'removed' nodes as the main categories. If that is okay, we can use
the same in the URL path-names instead of bl, ex. Better and full-forms are easy to remember
and pass around. Same in the Titles and corresponding variable names for the corresponding
 - Can we also print NodeState on the NodesPage? Definitely helps for the all-nodes case,
also distinguishes the type of a removed node - LOST vs DECOMMISIONED.

Also ran it on a single node. Looks clean except for two minor things - (1) the titles of
the new table are bolder than the other main-table - say apps-list and (2) it may be good
to have some gap between the metrics-table and the main-table for each of this pages. Please
see if these are doable, if it is too convoluted we can skip for now.

Thanks for taking this up! I am the biggest beneficiary in the short term, when I run benchmarks
and lots of jobs :)
> 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
> - 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


View raw message