[
https://issues.apache.org/jira/browse/YARN-9567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855530#comment-16855530
]
Tao Yang commented on YARN-9567:
--------------------------------
Some updates about this issue:
# Support summarizing app activities on nodes in multiple scheduling processes
to get the comprehensive information for better debugging, based on YARN-9578.
# Support partial refresh on app attempt page, so that we have two ways to get
diagnostics:
** When refresh the app attempt page, query and show activities directly from
cache.
** When click the refresh button, update activities immediately and get
activities and show them after about 2 seconds.
# Diagnostics information can be classified to 3 levels (request, app and
scheduler activities).
** Request level !image-2019-06-04-17-29-29-368.png|width=1287,height=90!
** App level !image-2019-06-04-17-31-31-820.png|width=648,height=63!
** Scheduler activities level
!image-2019-06-04-17-58-11-886.png|width=731,height=121!
Please feel free to give your suggestions!
I will attach the patch after its dependency issue YARN-9578 resolved.
> 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: image-2019-06-04-17-29-29-368.png,
> image-2019-06-04-17-30-40-990.png, image-2019-06-04-17-31-31-820.png,
> image-2019-06-04-17-58-11-886.png, 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: [email protected]
For additional commands, e-mail: [email protected]
