Thanks Vinay. Following up on this, in a multi-user environment, Livy will create a session (and a separate Spark job) for each user. If one user restarts the Livy interpreter, will that cause other users' sessions along with their Spark job to be killed?
If so, can I work around this by setting binding mode for the interpreter to always be private? On Thu, Aug 4, 2016 at 5:15 PM Vinay Shukla <vinayshu...@gmail.com> wrote: > Hi Chen, > > I agree this is not very user friendly & there should be no need to > restart LivyInterpreter. > One short term fix may be to increase the livy session timeout by changing > livy.server.session.timeout (takes time in millisecond) > > Filed https://issues.apache.org/jira/browse/ZEPPELIN-1293 to track it. > > Thanks, > Vinay > > > On Thu, Aug 4, 2016 at 12:57 PM, Chen Song <chen.song...@gmail.com> wrote: > >> Hi >> >> When using Zeppelin over Livy, it appears that Livy will delete the >> session (and terminate the Spark job) after one hour of inactivity. After >> that, the SparkContext is closed and the user will see an error like 404 >> Not Found in Zeppelin notebook. >> >> From this point, is the only way to proceed is to manually restart the >> interpreter? This is not very user-friendly. Is there a way for interpreter >> to reconnect itself to a new Livy session automatically? >> >> Chen >> > >
