[
https://issues.apache.org/jira/browse/YARN-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775700#comment-13775700
]
Jason Lowe commented on YARN-451:
---------------------------------
Is knowing how big an application might get in the future important? Knowing
how big an application is right now, both in terms of what it's using and what
it's asking for, seems more relevant for understanding why a queue is
overloaded or jobs aren't getting scheduled as quickly as expected. The
ApplicationResourceUsageReport already contains this information, and it should
be straightforward to report as part of the ApplicationResourceUsageReport for
display via the web UI, CLI, or REST services.
Note that YARN-415 is already attempting to do this for historical resource
usage so it will be easy to see which jobs have taken large amounts of
resources and could have slowed other jobs in the past.
> Add more metrics to RM page
> ---------------------------
>
> Key: YARN-451
> URL: https://issues.apache.org/jira/browse/YARN-451
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Affects Versions: 2.0.3-alpha
> Reporter: Lohit Vijayarenu
> Assignee: Sangjin Lee
> Priority: Blocker
> Attachments: in_progress_2x.png, yarn-451-trunk-20130916.1.patch
>
>
> ResourceManager webUI shows list of RUNNING applications, but it does not
> tell which applications are requesting more resource compared to others. With
> cluster running hundreds of applications at once it would be useful to have
> some kind of metric to show high-resource usage applications vs low-resource
> usage ones. At the minimum showing number of containers is good option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
