Rohith commented on YARN-3273:

Attached v2 patch for surfacing scheduler metrics. And attached the screenshot 
of changed UI page.
YARN-3273-am-resource-used-AND-User-limit-v2.PNG shows following metrics
# SchedulerMetrics table is added in front page. This table containes generic 
scheduler data like schedulerType,schedulerResourceType,min/max resource 
allocation. This table can be used in future for other common scheduler metrics 
to display.
# *Used Application Master Resources:* added for each leafqueue info.
#  Active users info table is added per CS#LeafQueue. This display user's 
ResourceLimit, ReusourceUsed,AM Resource,AM ResourceUsed and others. Since it 
is specific to CS, this is added in this page.

# For headroom, it is added only display block with empty data. Since headroom 
is not part of RMAppAttemptMetrics, retrieving this info directly from 
scheduler is tedious on the fly. Headroom need to be stored in either RMApp or 
RMAttempt state. I think headroom can be in RMAppAttemptMetric and render only 
if attempt is running. Any thoughts?

> 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, 0001-YARN-3273-v2.patch, 
> YARN-3273-am-resource-used-AND-User-limit-v2.PNG, 
> YARN-3273-am-resource-used-AND-User-limit.PNG, 
> YARN-3273-application-headroom-v2.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

Reply via email to