You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2017/06/16 23:35:00 UTC

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

     [ https://issues.apache.org/jira/browse/SPARK-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcelo Vanzin resolved SPARK-11058.
------------------------------------
    Resolution: Not A Problem

This is a limitation of client mode in Spark. The YARN application always shows up as successful. The {{SparkContext}} API is not rich enough for the driver to tell the AM whether to succeed or fail the YARN application.

> 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