Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/8007#discussion_r39097288
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/YarnSchedulerBackend.scala
---
@@ -90,6 +93,41 @@ private[spark] abstract class YarnSchedulerBackend(
}
}
+ override def createDriverEndpoint(properties: Seq[(String, String)]):
DriverEndpoint = {
+ new YarnDriverEndpoint(rpcEnv, properties)
+ }
+
+ /**
+ * Override the DriverEndpoint to add extra logic for the case when an
executor is disconnected.
+ * We should check the cluster manager and find if the loss of the
executor was caused by YARN
+ * force killing it due to preemption.
+ *
+ * Specifically, this endpoint is the endpoint used by
CoarseGrainedSchedulerBackend. Unlike
+ * YarnSchedulerEndpoint, it handles messages from executors the driver
is connected to. It
+ * does query the application master when the onDisconnected event is
received, however.
--- End diff --
This paragraph is kinda long-winded. I think it's OK to just say
```
This endpoint communicates with the executors and queries the AM for an
executor's
exit status when it is disconnected.
```
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
