[
https://issues.apache.org/jira/browse/SPARK-11854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014144#comment-15014144
]
sam edited comment on SPARK-11854 at 11/19/15 10:56 PM:
--------------------------------------------------------
[~srowen] It's on emr-4.1.0 with latest Spark EMR uses (so 1.5.0). My main
method throws an exception, so the driver, but I still get 0.
Sorry about cloning, I don't have reopen rights. Also I assumed there may be a
subtle difference since I'm in yarn-client mode, not yarn-cluster mode.
was (Author: sams):
[~srowen] It's on emr-4.1.0 with latest Spark EMR uses (so 1.5.1 I guess). My
main method throws an exception, so the driver, but I still get 0.
Sorry about cloning, I don't have reopen rights. Also I assumed there may be a
subtle difference since I'm in yarn-client mode, not yarn-cluster mode.
> The exit code of spark-submit is still 0 when an yarn application fails
> -----------------------------------------------------------------------
>
> Key: SPARK-11854
> URL: https://issues.apache.org/jira/browse/SPARK-11854
> Project: Spark
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.5.1
> Reporter: sam
> Assignee: Shixiong Zhu
> Labels: yarn
>
> When an yarn application fails (-yarn-cluster- yarn-client mode), the exit
> code of spark-submit is still 0. It's hard for people to write some automatic
> scripts to run spark jobs in yarn because the failure can not be detected in
> these scripts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
