Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/9963#discussion_r46385037
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -341,6 +341,24 @@ class CoarseGrainedSchedulerBackend(scheduler:
TaskSchedulerImpl, val rpcEnv: Rp
}
}
+ /**
+ * Reset the state of CoarseGrainedSchedulerBackend to the initial
state. Currently it will only
+ * be called in the yarn-client mode where AM is registered again, also
when dynamic
+ * allocation is enabled.
+ * */
+ protected def reset(): Unit = synchronized {
+ if (Utils.isDynamicAllocationEnabled(conf)) {
+ numPendingExecutors = 0
+ executorsPendingToRemove.clear()
+
+ // Remove all the lingering executors that should be removed but not
yet. The reason might be
+ // because (1) disconnected event is not yet received; (2) executors
die silently.
+ executorDataMap.foreach { case (eid, _) =>
+ driverEndpoint.askWithRetry[Boolean](RemoveExecutor(eid,
SlaveLost()))
--- End diff --
Looks like `RemoveExecutor` has a reply in the code:
```
case RemoveExecutor(executorId, reason) =>
removeExecutor(executorId, reason)
context.reply(true)
```
---
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]
