You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Victor Sunderland (Jira)" <ji...@apache.org> on 2025/08/20 03:51:00 UTC

[jira] [Commented] (SPARK-53335) Support diagnostics for jobs which ran on Kubernetes

    [ https://issues.apache.org/jira/browse/SPARK-53335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18015046#comment-18015046 ] 

Victor Sunderland commented on SPARK-53335:
-------------------------------------------

https://github.com/apache/spark/pull/52068

> Support diagnostics for jobs which ran on Kubernetes
> ----------------------------------------------------
>
>                 Key: SPARK-53335
>                 URL: https://issues.apache.org/jira/browse/SPARK-53335
>             Project: Spark
>          Issue Type: Improvement
>          Components: Kubernetes, Spark Core
>    Affects Versions: 4.1.0
>            Reporter: Victor Sunderland
>            Priority: Major
>
> For jobs which run on kubernetes there is no native concept of diagnostics (like there is in YARN), which means that for debugging and triaging errors users _must_ go to logs. For many jobs which run on YARN this is often not necessary, since the diagnostics contains the root cause reason for failure. Additionally, for platforms which provide automation of failure insights, or make decisions based on failures, there must be a custom solution or deciding why the application failed (e.g. log and stack trace parsing). We should provide a way for yarn-equivalent diagnostics for spark jobs on kubernetes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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