[ https://issues.apache.org/jira/browse/YARN-9567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tao Yang updated YARN-9567: --------------------------- Description: 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|width=793,height=248! (2) After requesting the application activities REST API, we can see diagnostics now. !show_diagnostics_after_requesting_app_activities_REST_API.png|width=1046,height=276! was: 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! > 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|width=793,height=248! > (2) After requesting the application activities REST API, we can see > diagnostics now. > !show_diagnostics_after_requesting_app_activities_REST_API.png|width=1046,height=276! > -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org