Ruslan Dautkhanov created ZEPPELIN-3256:

             Summary: ipython backend: capture when backend ipython process dies
                 Key: ZEPPELIN-3256
             Project: Zeppelin
          Issue Type: Bug
          Components: Core, pySpark, python-interpreter, zeppelin-interpreter
    Affects Versions: 0.7.3, 0.8.0
            Reporter: Ruslan Dautkhanov

Using `quit()` in the new ipython interpreter backend leads to ipython backend 
.. exiting, and a new paragraph run gets stuck in 'RUNNING' indefinitely, or at 
least until pySpark interpreter is restarted.

Two suggestions:
 # Ignore `quit()` callsĀ 
 # More importantly - capture when IPython backend process dies (for this any 
other) reason so Spark interpreter would know it has to start a new session, 
and so it would also not show misleading 'RUNNING' state indefinitely on the 

First one might be easy to fix using something `def quit(): pass` or something 
as soon as ipython process starts.

But again more importantly it would be great to capture and recognize events 
when ipython process exits or dies for some reason and pass this information up 
to Spark interpreter.

This message was sent by Atlassian JIRA

Reply via email to