Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8007#discussion_r37359214
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -207,6 +211,17 @@ private[yarn] class YarnAllocator(
}
/**
+ * Gets the executor loss reason for a disconnected executor.
+ * Note that this method is expected to be called exactly once per
executor ID.
+ */
+ def getExecutorLossReason(executorId: String): ExecutorLossReason =
synchronized {
+ allocateResources()
+ // Expect to be asked for a loss reason once and exactly once.
+ assert(completedExecutorExitReasons.contains(executorId))
--- End diff --
Your assumption probably holds for the preemption case, since it's YARN
killing the container. But I can imagine that if the container exits by itself,
it might be possible for the disconnect to reach the driver endpoint and the
`GetExecutorLossReason` message to reach the AM before the NM has had a chance
to process the container exit and communicate that to the RM.
---
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
