Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2011
For case 1, why not creating a new SparkContext ? `sc.stop` only cause the
spark app shutdown, but the remote interpreter process should still be alive.
Overall, I don't think restarting `SparkContext` implicitly for user is a
proper solution. This might cause confusion for users, as creating new
`SparkContext` means all the historical state is lost, user have to rerun all
the paragraphs. One proper solution I can think of is that send a warning
message to front end to tell user the SparkContext is dead for some unknown
reason, you need to either create a new one or restarting the interpreter.
---
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.
---
