Interpreters can be restarted from 'interpreter' menu, or individual user can restart interpreter in 'interpreter binding' menu on each Notes. Second method available in 0.7.0-SNAPSHOT.
'Job' menu (in 0.7.0-SNAPSHOT) supposed to provide at a glance view of all jobs running on Zeppelin and will help admin manage the resources. Hope this helps. Thanks, moon On Mon, Nov 7, 2016 at 3:21 PM York Huang <yorkhuang.d...@gmail.com> wrote: > Thanks moon. > > One more question may not be so related. How can user shut down individual > notebook and its interpreter? How does the administrator monitor the > running interpreter and shut it down if running out of resources? > > On 8 November 2016 at 05:33, moon soo Lee <m...@apache.org> wrote: > > Thanks Igor for valuable feedbacks. > For that reason, i've seen some companies instantiate Zeppelin inside of > container per person, or restrict usage of certain type of interpreters. > I expect Zeppelin will have impersonation soon and mitigate that problem > from the next release. > > York, > Yes, you can run multiple Zeppelin instances with different configurations. > bin/zeppelin-daemon.sh accepts --config parameter. You can have multiple > configuration directories and point them with --config parameter. > > Thanks, > moon > > On Sun, Nov 6, 2016 at 10:39 PM York Huang <yorkhuang.d...@gmail.com> > wrote: > > Also if I want to run all Zeppelin instances from one Linux machine, do I > have to create the Zeppelin binaries for each user with different ports so > that multiple instances can run in the same box? > > Sent from my iPhone > > On 7 Nov 2016, at 5:17 PM, Igor Yakushin <i...@uchicago.edu> wrote: > > Upon reading the documentation and coming with JupyterHub experience, it > was natural to assume that Zeppelin should run as root, one daemon for all > the users, especially considering that one can use it with ldap. > > One should put it into the documentation with big red letters: > *NEVER RUN ZEPPELIN AS ROOT !!! * > > Also, the daemon itself should check if it is running as root and die with > violent complaints if yes. This is a major security problem. > > This was not obvious at all to me that each user should run his own daemon > on his account. I know at least one more place that made the same mistake > as me and runs Zeppelin under root. > > >
