LUTZ Emeric created ZEPPELIN-3819:
-------------------------------------

             Summary: Livy interpreter : Long running job timeout
                 Key: ZEPPELIN-3819
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3819
             Project: Zeppelin
          Issue Type: Bug
          Components: livy-interpreter
    Affects Versions: 0.7.0
            Reporter: LUTZ Emeric


Launching a long running job (running time > livy session timeout) with the 
livy interpreter, like a file copy in spark, doesn't keep alive the livy 
session.

At the end of the livy session timeout set in the configuration, the session is 
killed and the job stopped.

Modifying the livy session timeout isn't a sustainable solution.

Idea : Keep alive the livy session while the job isn't finished (with the job 
PID)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to