tgravescs commented on a change in pull request #27636:
[SPARK-30873][CORE][YARN]Handling Node Decommissioning for Yarn cluster manger
in Spark
URL: https://github.com/apache/spark/pull/27636#discussion_r389689841
##########
File path: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
##########
@@ -1525,10 +1539,27 @@ private[spark] class DAGScheduler(
s" ${task.stageAttemptId} and there is a more recent attempt for
that stage " +
s"(attempt ${failedStage.latestInfo.attemptNumber}) running")
} else {
+ // Gracefully handling the stage abort due to fetch failure in the
+ // decommission nodes
+ if
(!event.reason.asInstanceOf[FetchFailed].countTowardsStageFailures) {
+ // Ignore stage attempts due to fetch failed only
Review comment:
I think comment should specifically say for decommission tracking.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
