Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17480
@witgo are you planning to update this PR to fix the behavior of `reset` in
call cases?
The biggest problem I have with this patch is that reading the code does
not give you any insight into why `initializing` has to be true or false, and
why that's related to this bug. And that's the main source of my previous
comments.
So in my view the right path here is to fix `reset()` so that it does the
right thing in all cases. And it seems to me the right thing is not to mess
with `initialize` or the driver's current idea of how many executors it needs.
---
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]
