[jira] [Commented] (SPARK-11058) failed spark job reports on YARN as successful

["Nick Dimiduk (JIRA)" <ji...@apache.org>]

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

Nick Dimiduk commented on SPARK-11058:
--------------------------------------

[~srowen], [~vanzin] this is still considered a not-fix issue? I see the same behavior with Spark 2.1.0 on Yarn 2.7.3. Job submitted to the cluster in client-mode, killed with SIGTERM results in an application in Yarn's job history with "YarnApplicationState: FINISHED" and "FinalStatus Reported by AM: SUCCEEDED". Surely this is a bug.

> failed spark job reports on YARN as successful
> ----------------------------------------------
>
>                 Key: SPARK-11058
>                 URL: https://issues.apache.org/jira/browse/SPARK-11058
>             Project: Spark
>          Issue Type: Bug
>          Components: YARN
>    Affects Versions: 1.3.0
>         Environment: CDH 5.4
>            Reporter: Lan Jiang
>            Priority: Minor
>
> I have a spark batch job running on CDH5.4 + Spark 1.3.0. Job is submitted in “yarn-client” mode. The job itself failed due to YARN kills several executor containers because the containers exceeded the memory limit posed by YARN. However, when I went to the YARN resource manager site, it displayed the job as successful. I found there was an issue reported in JIRA https://issues.apache.org/jira/browse/SPARK-3627, but it says it was fixed in Spark 1.2. On Spark history server, it shows the job as “Incomplete”. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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