[
https://issues.apache.org/jira/browse/SPARK-17769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Vanzin resolved SPARK-17769.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
> Some FetchFailure refactoring in the DAGScheduler
> -------------------------------------------------
>
> Key: SPARK-17769
> URL: https://issues.apache.org/jira/browse/SPARK-17769
> Project: Spark
> Issue Type: Improvement
> Components: Scheduler
> Reporter: Mark Hamstra
> Assignee: Mark Hamstra
> Priority: Minor
> Fix For: 2.2.0
>
>
> SPARK-17644 opened up a discussion about further refactoring of the
> DAGScheduler's handling of FetchFailure events. These include:
> * rewriting code and comments to improve readability
> * doing fetchFailedAttemptIds.add(stageAttemptId) even when
> disallowStageRetryForTest is true
> * issuing a ResubmitFailedStages event based on whether one is already
> enqueued for the current failed stage, not any prior failed stage
> * logging the resubmission of all failed stages
--
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
