We are implementing the exact same use case today , Trying out central shared zeppelin 0.7 instance in our organisation.
As member of admin team we have locked down the interpreter page and published set of settings which we have been configured in the backend. If Interpreter settings are per user basis then only we will give the ability to end user to change what he needs , and behaviour you mentioned about restart affecting only that user job seems a good idea. One of the issue we are facing is lifecycle of interpreters , zombie Zeppelin processes which are left on the node where Zeppelin is installed and on cluster. How does restart of interpreter by end users and people from admin team affect those processes ? Another issue to take care is which of the change will need Zeppelin server to be restarted as a whole ? I can write detailed note on issues we are having with running Zeppelin in enterprise if you are ready to take some feedback in future backlog. On 22 February 2017 at 19:17, Prabhjyot Singh <prabhjyotsi...@apache.org> wrote: > This is WRT the PR that I've created https://github.com/ > apache/zeppelin/pull/2034. > > The issue that I want to discuss over here is how should an Interpreter > behave when it is; > - restarted from notebook > - restarted from Interpreter setting page > - edited from Interpreter setting page > - deleted from Interpreter setting page > > > Assuming Zeppelin is being used in Enterprise world, where not all user > may have access to Zeppelin's Interpreter setting page, say only restricted > user say "admin-group" have access to this page. Now when a restart, edit > or delete action is performed from Interpreter setting page; any of this > operation should terminate all the processes of that particular > Interpreter. On the other hand if it is restarted from the notebook page by > any User, then only process of that logged-in User should get affected. > > How do you guys think of it? > > -- > > Warm Regards, > > Prabhjyot Singh >
