wypoon commented on a change in pull request #28848:
URL: https://github.com/apache/spark/pull/28848#discussion_r441865293
##########
File path:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala
##########
@@ -540,6 +540,46 @@ class DAGSchedulerSuite extends SparkFunSuite with
LocalSparkContext with TimeLi
assert(mapStatus2(2).location.host === "hostB")
}
+ test("[SPARK-32003] All shuffle files for executor should be cleaned up on
fetch failure") {
+ // reset the test context with the right shuffle service config
+ afterEach()
+ val conf = new SparkConf()
+ conf.set(config.SHUFFLE_SERVICE_ENABLED.key, "true")
+ init(conf)
+
+ val shuffleMapRdd = new MyRDD(sc, 3, Nil)
+ val shuffleDep = new ShuffleDependency(shuffleMapRdd, new
HashPartitioner(3))
+ val shuffleId = shuffleDep.shuffleId
+ val reduceRdd = new MyRDD(sc, 3, List(shuffleDep), tracker =
mapOutputTracker)
+
+ submit(reduceRdd, Array(0, 1, 2))
+ // Map stage completes successfully,
+ // two tasks are run on an executor on hostA and one on an executor on
hostB
+ complete(taskSets(0), Seq(
+ (Success, makeMapStatus("hostA", 3)),
+ (Success, makeMapStatus("hostA", 3)),
+ (Success, makeMapStatus("hostB", 3))))
+ // Now the executor on hostA is lost
+ runEvent(ExecutorLost("hostA-exec", ExecutorExited(-100, false, "Container
marked as failed")))
+
+ // The MapOutputTracker has all the shuffle files
+ val initialMapStatuses =
mapOutputTracker.shuffleStatuses(shuffleId).mapStatuses
+ assert(initialMapStatuses.count(_ != null) == 3)
+ assert(initialMapStatuses(0).location.executorId === "hostA-exec")
+ assert(initialMapStatuses(1).location.executorId === "hostA-exec")
+ assert(initialMapStatuses(2).location.executorId === "hostB-exec")
Review comment:
I adopted your suggestion but I just inlined the function.
----------------------------------------------------------------
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:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
