Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/5636#discussion_r38581951
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1240,10 +1243,17 @@ class DAGScheduler(
if (errorMessage.isEmpty) {
logInfo("%s (%s) finished in %s s".format(stage, stage.name,
serviceTime))
stage.latestInfo.completionTime = Some(clock.getTimeMillis())
+
+ // Clear failure count for this stage, now that it's succeeded.
+ // We only limit consecutive failures of stage attempts,so that if a
stage is
+ // re-used many times in a long-running job, unrelated failures
don't eventually cause the
+ // stage to be aborted.
+ stage.clearFailures()
--- End diff --
My understanding is that this is because the stage may need to be re-run
later if one of the machines where its output is stored fails, so the output
needs to be re-constructed
---
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]
