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

    https://github.com/apache/spark/pull/8093#discussion_r36784216
  
    --- Diff: 
core/src/main/scala/org/apache/spark/scheduler/cluster/YarnSchedulerBackend.scala
 ---
    @@ -110,6 +114,7 @@ private[spark] abstract class YarnSchedulerBackend(
             addWebUIFilter(filterName, filterParams, proxyBase)
     
           case RemoveExecutor(executorId, reason) =>
    +        logWarning(reason)
    --- End diff --
    
    Ah. I guess this is a side-effect of the race between the disconnect and 
the AM message. Because there's this code in `TaskSchedulerImpl`:
    
        override def executorLost(executorId: String, reason: 
ExecutorLossReason): Unit = {
          var failedExecutor: Option[String] = None
      
          synchronized {
            if (activeExecutorIds.contains(executorId)) {
              val hostPort = executorIdToHost(executorId)
              logError("Lost executor %s on %s: %s".format(executorId, 
hostPort, reason))



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