Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/19048
I'm not sure I understand why is this a problem. What is the undesired
behavior that happens because of this? That's not explained either in the PR
nor in the bug.
The way I understand the code, yes, there are potentially redundant calls
to update the target number of executors; but then, `ExecutorAllocationManager`
makes that call every time it wakes up (100ms), so it doesn't seem like that
causes any problems.
---
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
