GitHub user karuppayya opened a pull request:

    https://github.com/apache/zeppelin/pull/2011

    ZEPPELIN-2102: Restart interpreter automatically

    ### What is this PR for?
    Sparkcontext is shutdown in following cases
    1. calling `sc.stop` explicitly
    In this case, the user has to manually restart the interpreter to submit 
his next spark job
    2. OOM error from spark
    Restarting of interpreter will not help. The only recovery is restarting 
zeppelin server
    I have not enumerated all the cases in which sc can go down. There might be 
other cases.
    In this PR, restarting interpreter automatically
    
    ### What type of PR is it?
    Improvement
    
    ### Todos -NA
    
    ### What is the Jira issue?
    ZEPPELIN-2102
    
    ### How should this be tested?
    1. Run `sc.stop`. Subsequently run another paragraph
    2.  Cause spark driver to crash due to OOM, run subsequent spark paragraph
    
    ### Screenshots (if appropriate) NA
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/karuppayya/incubator-zeppelin ZEPPELIN-2102

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/2011.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2011
    
----
commit 752a42368601f1b531654c6e9fab139b8b5b430f
Author: karuppayya <karuppay...@qubole.com>
Date:   2017-02-12T14:38:29Z

    Restart interpreter automatically

----


---
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.
---

Reply via email to