[
https://issues.apache.org/jira/browse/SPARK-53335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongjoon Hyun updated SPARK-53335:
----------------------------------
Parent: SPARK-54016
Issue Type: Sub-task (was: Improvement)
> Support diagnostics for jobs which ran on Kubernetes
> ----------------------------------------------------
>
> Key: SPARK-53335
> URL: https://issues.apache.org/jira/browse/SPARK-53335
> Project: Spark
> Issue Type: Sub-task
> Components: Kubernetes, Spark Core
> Affects Versions: 4.1.0
> Reporter: Victor Sunderland
> Priority: Major
> Labels: pull-request-available
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
