Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7888#discussion_r44725439
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -1489,7 +1489,7 @@ class SparkContext(config: SparkConf) extends Logging
with ExecutorAllocationCli
private[spark] def killAndReplaceExecutor(executorId: String): Boolean =
{
schedulerBackend match {
case b: CoarseGrainedSchedulerBackend =>
- b.killExecutors(Seq(executorId), replace = true)
+ b.killExecutors(Seq(executorId), replace = true, force = false)
--- End diff --
Why is this one `force = false`? This is most probably the cause of the
failure in the heartbeat test; if the executor is not heartbeating, the driver
should forcefully kill it, regardless of whether tasks are currently assigned
to it.
---
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]
