Github user juliuszsompolski commented on a diff in the pull request: https://github.com/apache/spark/pull/22209#discussion_r214381992 --- Diff: core/src/main/scala/org/apache/spark/status/AppStatusListener.scala --- @@ -350,11 +350,20 @@ private[spark] class AppStatusListener( val e = it.next() if (job.stageIds.contains(e.getKey()._1)) { val stage = e.getValue() - stage.status = v1.StageStatus.SKIPPED - job.skippedStages += stage.info.stageId - job.skippedTasks += stage.info.numTasks - it.remove() - update(stage, now) + if (v1.StageStatus.PENDING.equals(stage.status)) { --- End diff -- In the previous behaviour, it would have marked the stages that were ACTIVE as SKIPPED, which now will not happen here anymore. It looks like the code in `onStageCompleted` may handle that in the `stage.status = event.stageInfo.failureReason match {` handles that. Is that the case?
--- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org