hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3273) Improve web UI to facilitate scheduling analysis and debugging
Date Mon, 09 Mar 2015 04:41:38 GMT

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

Rohith commented on YARN-3273:

bq. The headroom need not be part of RMAppAttemptMetrics, as it only makes sense for running
I will verify in latest trunk and change accordingly.

bq. CapacitySchedulerLeafQueueInfo#aMResourceLimit - this is not part of your patch; would
you mind changing the “a” to “A” here. The name is important as it’s exposed in
rest api
OK, will change in next patch.

bq. Regarding the per user info: do you think it’s useful to have a separate top-level users
link on the front page within which we show a list of users info such as totalResourceUsage,
amResourceUsage, totalResourceLimit, amResourceLimit
This is good Idea. I think we can keep existing as it is i.e *Used Application Master Resources
Per User* , *Used Application Master Resources:* and *Max Resources Per User:* because if
no active users are there then this dispaly nothing. 
And separate user table that display content of ActiveUsers info along with TotalResourceLimit
for user and AMResourceLimit for User. Any more fields need to add here?
||Users||ResourceLimit||Used Resource||AMResourceLimit||User AMResource||PendingApplications||ActiveApplications

bq. We have a LeafQueue#computeUserLimit method to compute user-limit; we may add a new resourceLimit
field in LeafQueue#User class and when LeafQueue#computeUserLimit is called, set the resourceLimit
into LeafQueue#User#resourceLimit.

> Improve web UI to facilitate scheduling analysis and debugging
> --------------------------------------------------------------
>                 Key: YARN-3273
>                 URL: https://issues.apache.org/jira/browse/YARN-3273
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Jian He
>            Assignee: Rohith
>         Attachments: 0001-YARN-3273-v1.patch, YARN-3273-am-resource-used-AND-User-limit.PNG,
> Job may be stuck for reasons such as:
> - hitting queue capacity 
> - hitting user-limit, 
> - hitting AM-resource-percentage 
> The  first queueCapacity is already shown on the UI.
> We may surface things like:
> - what is user's current usage and user-limit; 
> - what is the AM resource usage and limit;
> - what is the application's current HeadRoom;

This message was sent by Atlassian JIRA

View raw message