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 Tue, 10 Mar 2015 04:37:38 GMT

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

Rohith commented on YARN-3273:

Thanks Jian He for your suggestion:-) 
Overall summary to be in right direction. I am assuming that all scheduler changes is only
for CS. Is there any common scheduelr changes to be done ?
# Headroom will be dispalyed in application attempt page. This will be set as 0 once the attempt
is finished.
# For each leaf queue in CS, UsedAMResource,UsedUserAMResource, 'User Limit for User' will
be displayed.
# In Active User, for each user link will be provided which redirect to additional filtered
user page containing userInfo in table as above sample table. This is also applicable only
for CS.
# All active users table wont be rendered. Instead only link will be provided for each user
i.e step-3 in active user. Am I understading is correct?

> 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