You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Reynold Xin (JIRA)" <ji...@apache.org> on 2016/09/28 23:30:20 UTC
[jira] [Resolved] (SPARK-17644) The failed stage never resubmitted
due to abort stage in another thread
[ https://issues.apache.org/jira/browse/SPARK-17644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reynold Xin resolved SPARK-17644.
---------------------------------
Resolution: Fixed
Assignee: Fei Wang
Fix Version/s: 2.1.0
2.0.1
> The failed stage never resubmitted due to abort stage in another thread
> -----------------------------------------------------------------------
>
> Key: SPARK-17644
> URL: https://issues.apache.org/jira/browse/SPARK-17644
> Project: Spark
> Issue Type: Bug
> Components: Scheduler, Spark Core
> Affects Versions: 1.6.0, 2.0.0
> Reporter: Fei Wang
> Assignee: Fei Wang
> Fix For: 2.0.1, 2.1.0
>
>
> there is a race condition when FetchFailed and resubmit failed stage:
> job1, job2 run in different threads, if job 1 failed 4 times due to fetchfailed and aborted, then job2 can not post ResubmitFailedStages becase the failedStages in DAGScheduler is not empty now.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org