Github user rdblue commented on a diff in the pull request:
https://github.com/apache/spark/pull/17813#discussion_r114166764
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -589,8 +605,18 @@ class CoarseGrainedSchedulerBackend(scheduler:
TaskSchedulerImpl, val rpcEnv: Rp
// take into account executors that are pending to be added or
removed.
val adjustTotalExecutors =
if (!replace) {
- doRequestTotalExecutors(
- numExistingExecutors + numPendingExecutors -
executorsPendingToRemove.size)
+ requestedTotalExecutors = math.max(requestedTotalExecutors -
executorsToKill.size, 0)
+ if (requestedTotalExecutors !=
--- End diff --
Yes, it would. I can change it to debug or remove it. This was mainly for
us to see how often it happened. With the fix to the request timing, this
doesn't tend to happen at all. It is just if the method is called every 100ms
that you see the behavior all the time because there isn't enough time for
kills and requests to complete before recomputing.
---
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]
