hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tao Yang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-9567) Add diagnostics for outstanding resource requests on app attempts page
Date Mon, 20 May 2019 13:15:00 GMT

     [ https://issues.apache.org/jira/browse/YARN-9567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tao Yang updated YARN-9567:
    Attachment:     (was: show_diagnostics_after_requesting_app_activities_REST_API.png)

> Add diagnostics for outstanding resource requests on app attempts page
> ----------------------------------------------------------------------
>                 Key: YARN-9567
>                 URL: https://issues.apache.org/jira/browse/YARN-9567
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>            Reporter: Tao Yang
>            Assignee: Tao Yang
>            Priority: Major
>         Attachments: no_diagnostic_at_first.png, show_diagnostics_after_requesting_app_activities_REST_API.png
> Currently on app attempt page we can see outstanding resource requests, it will be helpful
for users to know why if we can join diagnostics of this app with these. 
> Discussed with [~cheersyang], we can passively load diagnostics from cache of completed
app activities instead of actively triggering which may bring uncontrollable risks.
> For example:
> (1) At first we can see no diagnostic in cache if app activities not triggered below
the outstanding requests.
> !no_diagnostic_at_first.png!
> (2) After requesting the application activities REST API, we can see diagnostics now.
> !show_diagnostics_after_requesting_app_activities_REST_API.png!

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message