Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/2127#discussion_r16757427
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1045,21 +1045,19 @@ class DAGScheduler(
stage.pendingTasks += task
case FetchFailed(bmAddress, shuffleId, mapId, reduceId) =>
- // Mark the stage that the reducer was in as unrunnable
val failedStage = stageIdToStage(task.stageId)
- markStageAsFinished(failedStage, Some("Fetch failure"))
- runningStages -= failedStage
- // TODO: Cancel running tasks in the stage
- logInfo("Marking " + failedStage + " (" + failedStage.name +
- ") for resubmision due to a fetch failure")
- // Mark the map whose fetch failed as broken in the map stage
val mapStage = shuffleToMapStage(shuffleId)
- if (mapId != -1) {
- mapStage.removeOutputLoc(mapId, bmAddress)
- mapOutputTracker.unregisterMapOutput(shuffleId, mapId, bmAddress)
+ // It is likely that we receive multiple FetchFailed for a single
stage (because we have
+ // multiple tasks running concurrently on different executors). In
that case, it is possible
+ // the fetch failure has already been handled by the scheduler.
+ if (runningStages.contains(failedStage)) {
+ markStageAsFinished(failedStage, Some("Fetch failure"))
+ runningStages -= failedStage
+ // TODO: Cancel running tasks in the stage
+ logInfo(s"Marking $failedStage (${failedStage.name}) for
resubmision " +
--- End diff --
I'll tune up these log messages and merge this - thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
