[
https://issues.apache.org/jira/browse/SPARK-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953184#comment-14953184
]
Lan Jiang commented on SPARK-11058:
-----------------------------------
Sean,
Thanks for your comments. I made it critical because
"https://issues.apache.org/jira/browse/SPARK-3627"; was marked as critical. But
I am fine with "minor". The job was not successful. It lost a few executors and
had "incomplete" status in the spark history server. The job has 2 stages and
the second stage did not even start. This is a scala spark application, not
pyspark.
Lan
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
