From 58f646eee88bde40b0f4e6440c2af61a2b90364b Mon Sep 17 00:00:00 2001 From: Wenchen Fan Date: Wed, 6 Mar 2019 00:59:17 +0800 Subject: [PATCH] revert adding volatile --- .../main/scala/org/apache/spark/scheduler/TaskSetManager.scala | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala b/core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala index 59b931f33c902..453939aaf1901 100644 --- a/core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala +++ b/core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala @@ -123,7 +123,7 @@ private[spark] class TaskSetManager( // state until all tasks have finished running; we keep TaskSetManagers that are in the zombie // state in order to continue to track and account for the running tasks. // TODO: We should kill any running task attempts when the task set manager becomes a zombie. - @volatile private[scheduler] var isZombie = false + private[scheduler] var isZombie = false // Whether the taskSet run tasks from a barrier stage. Spark must launch all the tasks at the // same time for a barrier stage.