[ZEPPELIN-3246] Need option for automatically restart the livy interpreter automatically as zeppelin does not start new Livy session if yarn livy session application is killed

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7.3, 0.8.0
• Fix Version/s: 0.8.0
• Component/s: zeppelin-interpreter
• Assignee: Jeff Zhang
• Reporter: Franklinsam Paul
• Created: 19/Feb/18 10:22
• Updated: 06/Mar/18 07:30
• Resolved: 26/Feb/18 09:21

Description

Scenario:
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 Error".
Zeppelin still try to connect to previous livy session which is killed. It does not start new session.

Bug fix  for https://issues.apache.org/jira/browse/ZEPPELIN-2988 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.

 

Issue Links

• links to: GitHub Pull Request #2818