Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/5636#discussion_r36260921
--- Diff: core/src/main/scala/org/apache/spark/scheduler/Stage.scala ---
@@ -76,6 +77,35 @@ private[spark] abstract class Stage(
*/
private var _latestInfo: StageInfo = StageInfo.fromStage(this,
nextAttemptId)
+ /**
+ * Spark is resilient to executors dying by retrying stages on
FetchFailures. Here, we keep track
+ * of unique stage failures (per stage attempt) triggered by fetch
failures to prevent endless
+ * stage retries. Specifically, per stage we wish to only record a
failure when the following
+ * holds:
+ *
+ * A) A fetch failure was observed
+ * B) A failure has not yet been registered for this stage attempt.
There may be multiple
+ * concurrent failures for a sinlge stage since we may have multiple
tasks executing at the same
+ * time, one or many of which may fail. Also, even though there may only
be one non-zombie stage
+ * attemp, zombie stages may still have running tasks.
--- End diff --
typo: attemp
also just to be super-clear, "zombie stage attempts may still ..."
---
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]
