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 "chhinlinghean (Jira)" <ji...@apache.org> on 2026/09/29 06:52:00 UTC

[jira] [Assigned] (YARN-10323) [Umbrella] YARN Diagnostic collector

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

chhinlinghean reassigned YARN-10323:
------------------------------------

    Assignee: chhinlinghean

> [Umbrella] YARN Diagnostic collector
> ------------------------------------
>
>                 Key: YARN-10323
>                 URL: https://issues.apache.org/jira/browse/YARN-10323
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Szilard Nemeth
>            Assignee: chhinlinghean
>            Priority: Major
>         Attachments: YARN-10323 Design of Diagnostics Collector.pdf
>
>
> Troubleshooting YARN problems can be difficult on a production environment.
>  Collecting data before problems occur or actively collecting data in an on-demand basis could truly help tracking down issues.
> Some examples: 
>  1. If application is hanging, application logs along with RM / NM logs could be collected, plus jstack of either the YARN daemons or the application container.
>  2. Similarly, when an application fails we may collect data.
>  3. Scheduler issues are quite common so good tooling that helps to spot issues would be crucial.
> Design document in the attachments section.



--
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