Franklinsam Paul created ZEPPELIN-3246:

             Summary: Need option for automatically restart the livy 
interpreter automatically as zeppelin does not start new Livy session if yarn 
livy session application is killed
                 Key: ZEPPELIN-3246
             Project: Zeppelin
          Issue Type: Improvement
          Components: zeppelin-interpreter
    Affects Versions: 0.7.3, 0.8.0
            Reporter: Franklinsam Paul

1) Create a livy notebook
2) run 2 paragraph ( Make sure a livy session yarn application is started )
3) Clone livy notebook 
4) Kill yarn livy application
5) Run paragraphs from Clone livy notebook
Here, Cloned notebook para fails with 
"org.springframework.web.client.HttpServerErrorException: 500 Internal Server 
Zeppelin still try to connect to previous livy session which is killed. It does 
not start new session.

Bug fix  for is only 
improves the error message when the livy session is dead.  In a scenario where 
user makes a mistake in a query, he might need  to kill the job, but killing 
yarn livy session makes the interpreter inaccessible for all the users. It 
would be more reasonable to generate a notification (to  investigate the cause 
why the session has been dead) on the yarn livy session's dead following by an 
automatic interpreter restart to restore the service quickly without manual 
intervention. At-least this auto restart of interpreter could be provided as a 
optional feature or a possible workaround without manual intervention could be 
very helpful.


This message was sent by Atlassian JIRA

Reply via email to