[
https://issues.apache.org/jira/browse/SPARK-26365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224648#comment-17224648
]
Oscar Cassetti commented on SPARK-26365:
----------------------------------------
[~itayb] I have a patch [^spark-3.0.0-raise-exception-k8s-failure.patch]
which I tested for spark-3.0.0. It is not pretty but it does the job
I also have one for v2.4.5 [^spark-2.4.5-raise-exception-k8s-failure.patch]
again the code is a bit ugly but I have been using it in production since June
> spark-submit for k8s cluster doesn't propagate exit code
> --------------------------------------------------------
>
> Key: SPARK-26365
> URL: https://issues.apache.org/jira/browse/SPARK-26365
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes, Spark Core, Spark Submit
> Affects Versions: 2.3.2, 2.4.0
> Reporter: Oscar Bonilla
> Priority: Minor
> Attachments: spark-2.4.5-raise-exception-k8s-failure.patch,
> spark-3.0.0-raise-exception-k8s-failure.patch
>
>
> When launching apps using spark-submit in a kubernetes cluster, if the Spark
> applications fails (returns exit code = 1 for example), spark-submit will
> still exit gracefully and return exit code = 0.
> This is problematic, since there's no way to know if there's been a problem
> with the Spark application.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
