jiangxb1987 commented on a change in pull request #27223: [SPARK-30511][CORE] 
Spark marks intentionally killed speculative tasks as pending leads to holding 
idle executors
URL: https://github.com/apache/spark/pull/27223#discussion_r367700155
 
 

 ##########
 File path: core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala
 ##########
 @@ -614,18 +614,24 @@ private[spark] class ExecutorAllocationManager(
             stageAttemptToNumRunningTask -= stageAttempt
           }
         }
-        // If the task failed, we expect it to be resubmitted later. To ensure 
we have
-        // enough resources to run the resubmitted task, we need to mark the 
scheduler
-        // as backlogged again if it's not already marked as such (SPARK-8366)
-        if (taskEnd.reason != Success) {
-          if (totalPendingTasks() == 0) {
-            allocationManager.onSchedulerBacklogged()
-          }
-          if (taskEnd.taskInfo.speculative) {
-            stageAttemptToSpeculativeTaskIndices.get(stageAttempt).foreach 
{_.remove(taskIndex)}
-          } else {
-            stageAttemptToTaskIndices.get(stageAttempt).foreach 
{_.remove(taskIndex)}
-          }
+
+        if (taskEnd.taskInfo.speculative) {
+          stageAttemptToSpeculativeTaskIndices.get(stageAttempt).foreach 
{_.remove{taskIndex}}
+          stageAttemptToNumSpeculativeTasks(stageAttempt) -= 1
+        }
+
+        // If the task failed (not intentionally killed), we expect it to be 
resubmitted later. To
+        // ensure we have enough resources to run the resubmitted task, we 
need to mark the
+        // scheduler as backlogged again if it's not already marked as such 
(SPARK-8366)
+        taskEnd.reason match {
+          case Success | _: TaskKilled =>
 
 Review comment:
   Why do we want to include `TaskKilled` here? It's not quite straight forward 
to me

----------------------------------------------------------------
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]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to