You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Nandor Kollar (JIRA)" <ji...@apache.org> on 2017/12/04 09:45:00 UTC
[jira] [Commented] (SPARK-7953) Spark should cleanup output dir if
job fails
[ https://issues.apache.org/jira/browse/SPARK-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276535#comment-16276535 ]
Nandor Kollar commented on SPARK-7953:
--------------------------------------
[~joshrosen] could you please help me with this issue, is this still an outstanding bug? It looks like Spark. 2.2 already includes SPARK-18219, and it seems that the new commit protocol calls abortJob and abortTask.
> Spark should cleanup output dir if job fails
> --------------------------------------------
>
> Key: SPARK-7953
> URL: https://issues.apache.org/jira/browse/SPARK-7953
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.3.0
> Reporter: Mohit Sabharwal
>
> MR calls abortTask and abortJob on the {{OutputCommitter}} to clean up the temporary output directories, but Spark doesn't seem to be doing that (when outputting an RDD to a Hadoop FS)
> For example: {{PairRDDFunctions.saveAsNewAPIHadoopDataset}} should call {{committer.abortTask(hadoopContext)}} in the finally block inside the writeShard closure. And also {{jobCommitter.abortJob(jobTaskContext, JobStatus.State.FAILED)}} should be called if the job fails.
> Additionally, MR removes the output dir if job fails, but Spark doesn't.
--
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