[
https://issues.apache.org/jira/browse/YARN-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792908#comment-13792908
]
Jason Lowe commented on YARN-451:
---------------------------------
I wasn't proposing current consumption and total, rather current consumption
and ask (or current requests), although one can back-calculate ask from total
given current. The current consumption lets us quickly find the biggest apps
in the cluster, while the current ask lets us quickly find the apps that are
starving for more resources (beyond the ones that are UNASSIGNED).
If we only can pick one, I'd say go with current consumption. Usually users
know when their jobs are getting starved, and they want to know which jobs are
filling up the queue.
> 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 was sent by Atlassian JIRA
(v6.1#6144)
