Github user sitalkedia commented on the issue:
https://github.com/apache/spark/pull/19048
>>Or it can call killExecutors() like it does today and then call
requestTotalExecutors right after, same result without the awkwardness of the
parameter name, but that adds a trip to the cluster manager.
Okay, that seems like a reasonable hack. Only downside as you mentioned is
extra trip to the CM and adding more confusion to the usage of
`ExecutorAllocationClient` :/. But like you mentioned, cleaning up the api will
be a much larger change which is outside of the scope of this PR. I will make
the change as you suggested soon.
---
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]
