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 Fri, 06 Mar 2015 06:49:38 GMT

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

Rohith commented on YARN-3273:
------------------------------

There are 4 metrics are displayed.
# Application current headroom : this is the headroom being sent to application master in
heartbeat. Once the application is over, this value displayed as 0.
# Used Application Master Resource : fetched from queueUsage. If the 1st application AM itself
has greater than Max AM Resources then the application is submitted with higher resource only.
This is current behaviour. Because of this if user is submitted with higher resource(1st app)
then the User AM Resource display higher value than Max AM resource. 
# Used Application Master Resource per user : fetched from UserInfo. Display list of active
users used resources per queue level
# Max Resources Per User : This is calculated with the calculation below.
{code}
 public synchronized Resource getUserResourceLimit() {
    return Resources.multiplyAndNormalizeUp(resourceCalculator,
        absoluteCapacityResource, (userLimit / 100.0f) * userLimitFactor,
        minimumAllocation);
  }
{code}

Kindly review the patch

> 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,
YARN-3273-application-headroom.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
(v6.3.4#6332)

Mime
View raw message