You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zeppelin.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2015/12/28 22:05:49 UTC

[jira] [Created] (ZEPPELIN-539) RemoteInterpreter Heartbeat

Jungtaek Lim created ZEPPELIN-539:
-------------------------------------

             Summary: RemoteInterpreter Heartbeat
                 Key: ZEPPELIN-539
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-539
             Project: Zeppelin
          Issue Type: New Feature
          Components: zeppelin-interpreter
            Reporter: Jungtaek Lim


>From ZEPPELIN-535, I addressed that remote interpreter can become not able to respond for some circumstances, for example, OOME.

There're two scenarios, which one is that remote interpreter is not killed but not respond, another one is that remote interpreter is killed.

https://gist.github.com/HeartSaVioR/26190a71df6815aa62b8
https://gist.github.com/HeartSaVioR/d5049e7464534c48b4bf

Determining such scenarios requires analysis of Zeppelin's logs which seems not easy thing to normal users, and users cannot do within Zeppelin UI.
Furthermore, in order to make it back to normal, users should restart interpreter by hand.

It would be help to users when Zeppelin determines remote interpreter's status and let users know when it's not able to respond.
It would be more better to restore remote interpreter if possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)