Hi Chen,
1. Currently, Interpreter binding mode is more like whether each Note will
have a separate Interpreter session(scoped/isolated) or not(shared), rather
than per user.
https://issues.apache.org/jira/browse/ZEPPELIN-1210 will bring interpreter
session per user in the Zeppelin server side, bu
Few more follow-up questions to see if anyone has insights on them
1. What is the recommended way of interpreter binding mode setting Zeppelin
over Livy in a multi-user environment?
2. Is there a way to allow the user restart interpreter but restrict the
user from changing interpreter configs.
3.
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
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 tra
