You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/09/29 07:12:00 UTC
[jira] [Updated] (YARN-11996) Extend the Capacity Scheduler UI Diagnostic feature to collect the debugging artifacts
[ https://issues.apache.org/jira/browse/YARN-11996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated YARN-11996:
----------------------------------
Labels: pull-request-available (was: )
> Extend the Capacity Scheduler UI Diagnostic feature to collect the debugging artifacts
> --------------------------------------------------------------------------------------
>
> Key: YARN-11996
> URL: https://issues.apache.org/jira/browse/YARN-11996
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: chhinlinghean
> Assignee: chhinlinghean
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2026-09-29-13-50-49-306.png, image-2026-09-29-13-50-56-707.png
>
>
> The new Capacity Scheduler UI already have the diagnostics feature for debugging scheduler related issue. Instead of calling the new Diagnostic Collector endpoints from
> [YARN-10421|https://github.com/apache/hadoop/pull/8762#top], it is better to adapt to the new UI calling each diagnostic endpoint by checking the boxes.
> !image-2026-09-29-13-50-56-707.png!
> Therefore, the diagnostic UI should be extended to include the following endpoints:
> 1. JStacks for ResourceManager - `\{rm_address}/ws/v1/cluster/jstack/\{numberOfJStack}`
> 2. Bulk activities - `\{rm_address}/ws/v1/cluster/scheduler/bulk-activities`
> It is an architectural challenge to include the RM Debug log for the 2mins interval, therefore I omit it for now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org