Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/19048
Well, that's adding an API that does the same thing as existing APIs but a
little bit differently. In my view that adds to the problem, instead of fixing
it. Now every caller into the `ExecutorAllocationClient` has its own version of
the API that does things the exact way they want.
For example: the `replace` argument of the existing API is pretty much the
functionality you want. The EAM can call `requestTotalExecutors` right before
it calls `killExecutors(replace = true)` and achieve what it wants. It's just
awkwardly named in this context.
---
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
