Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5523#issuecomment-93716364
Have a look at
https://github.com/apache/spark/commit/de4fa6b6d12e2bee0307ffba2abfca0c33f15e45
which may resolve the issue of bad state after construction.
I don't think it's correct to make callers check some status of
`SparkContext` to decide whether calling a method is safe. `stop()` should
handle this. I don't think you can call `stop()` just because you didn't hear
from executors recently.
---
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]
