Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38340804
Hi, all, I read all your comments carefully, I agree with that killing the
SparkContext may be a better solution for now... Thank you very much for your
suggestions
but shall we kill the driver program instead of just call
SparkContext.stop? because it's very likely for the application to continue
even the SparkContext has been killed in a standalone application
if that's the case, the user will meet a NPE because taskScheduler in
SparkContext is null after calling sc.stop() (if the user wants to start new
task) (to reproduce this, you can call sc.textFile after sc.stop() is
called....)
---
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.
---
