Github user pwendell commented on a diff in the pull request:

    https://github.com/apache/spark/pull/3483#discussion_r21008461
  
    --- Diff: 
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
 ---
    @@ -127,7 +127,13 @@ class CoarseGrainedSchedulerBackend(scheduler: 
TaskSchedulerImpl, val actorSyste
             makeOffers()
     
           case KillTask(taskId, executorId, interruptThread) =>
    -        executorDataMap(executorId).executorActor ! KillTask(taskId, 
executorId, interruptThread)
    +        executorDataMap.get(executorId) match {
    +          case Some(executorInfo) =>
    +            executorInfo.executorActor ! KillTask(taskId, executorId, 
interruptThread)
    +          case None =>
    +            // Ignoring the task kill since the executor is not registered.
    +            logWarning(s"Attempted to kill task $taskId for unknown 
executor $executorId.")
    +        }
    --- End diff --
    
    IMO the current approach is more explicit and readable, even if someone is 
not a scala expert. Using `getOrElse` to just have a side effect of printing a 
log statement is also a bit awkward.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to