[
https://issues.apache.org/jira/browse/SPARK-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153777#comment-14153777
]
Thomas Graves commented on SPARK-3627:
--------------------------------------
As far as I am aware the common cases worked in 1.1. I didn't do an extensive
test run like I did with the pr here though so its possible some were broken.
Note there has always been the case where yarn-client mode doesn't report the
correct failure case because the AM doesn't know what happened on the client
side. That isn't fixed by this jira either.
I guess I propose we file a separate jira for that if there are known cases or
if we just want to go do a full test run. The code is quite different now too
so would require a separate pr anyway.
> spark on yarn reports success even though job fails
> ---------------------------------------------------
>
> Key: SPARK-3627
> URL: https://issues.apache.org/jira/browse/SPARK-3627
> Project: Spark
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.2.0
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Priority: Critical
>
> I was running a wordcount and saving the output to hdfs. If the output
> directory already exists, yarn reports success even though the job fails
> since it requires the output directory to not be there.
--
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
