You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "jiaan.geng (Jira)" <ji...@apache.org> on 2020/06/19 02:39:00 UTC
[jira] [Updated] (SPARK-31845) DAGSchedulerSuite: Reuse
completeNextStageWithFetchFailure
[ https://issues.apache.org/jira/browse/SPARK-31845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jiaan.geng updated SPARK-31845:
-------------------------------
Summary: DAGSchedulerSuite: Reuse completeNextStageWithFetchFailure (was: DAGSchedulerSuite: Improve and reuse completeNextStageWithFetchFailure)
> DAGSchedulerSuite: Reuse completeNextStageWithFetchFailure
> ----------------------------------------------------------
>
> Key: SPARK-31845
> URL: https://issues.apache.org/jira/browse/SPARK-31845
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 3.1.0
> Reporter: jiaan.geng
> Priority: Major
>
> DAGSchedulerSuite provides completeNextStageWithFetchFailure to make next stage occurs fetch failure.
> But many test case uses complete directly as follows:
> {code:java}
> complete(taskSets(2), Seq(
> (FetchFailed(BlockManagerId("hostA-exec2", "hostA", 12345),
> firstShuffleId, 0L, 0, 0, "ignored"),
> null)
> ))
> {code}
> We need to improve completeNextStageWithFetchFailure and reuse it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org