Yes, user isolated only works for Spark. The problem with running only user isolated is that then we get conflicts in the Scala REPL -- e.g. the same variable name cannot be used in multiple notebooks.
On Sun, Jul 28, 2019 at 9:10 PM Jeff Zhang <zjf...@gmail.com> wrote: > Hmm, that's right. Does only user isolated work for you ? > > Dima Kamalov <dimakama...@asana.com> 于2019年7月29日周一 下午12:03写道： > >> This does not fix the problem when a Spark session crashes. If a user >> has multiple notes in scoped mode, restarting one note will not restart the >> interpreter group -- it will only restart the session. This will restart >> the Scala REPL but not e.g. the Spark session. >> >> On Sun, Jul 28, 2019 at 6:16 PM Jeff Zhang <zjf...@gmail.com> wrote: >> >>> Restarting interpreter in note page will only restart that note's >>> owner's interpreter, won't affect other users' interpreter. >>> >>> >>> Dima Kamalov <dimakama...@asana.com> 于2019年7月27日周六 上午9:51写道： >>> >>>> Hi, >>>> >>>> I'm wondering whether there are any best practices around restarting a >>>> user's interpreter group. (E.g. the whole set of sessions for that user, >>>> but not sessions for other users.) >>>> >>>> Here's the problem I want to solve: >>>> >>>> - We are primarily using Zeppelin for the spark interpreter. Because >>>> each user has a number of notebooks, it seemed like a good idea to pool >>>> spark sessions per user so we did that by setting spark interpreter to user >>>> isolated, note scoped. >>>> - Periodically, a user's spark session will crash for whatever reason. >>>> >>>> Here's the possible solutions that I can think of. We're currently >>>> using 1a. >>>> (1) Within existing interpreter mode >>>> a. Restart the spark interpreter from the interpreter menu. This >>>> restarts it for ~30 users, so it's inconvenient to do often. >>>> b. Track down all of a user's notebooks, and restart the spark >>>> interpreter in each notebook. >>>> >>>> (2) Considering switching interpreter modes >>>> a. User isolated, note isolated -- our biggest concern with this is >>>> just the number of spark sessions that would get generated. Maybe this >>>> would play well with lifecycle management? >>>> b. User isolated -- seems a little bad for users because a variable >>>> updated in one note would overwrite the same variable in another note. >>>> >>>> (3) Work on a change to Zeppelin, assuming this feature doesn't exist >>>> yet >>>> a. In the interpreter menu, we can have the restart option ask whether >>>> to restart the interpreter only for the user or globally? Or maybe it only >>>> makes sense to allow to restarting it for the user? It seems like there's >>>> a more major undertaking for >>>> https://issues.apache.org/jira/browse/ZEPPELIN-1338 so I don't want to >>>> conflict with that direction. >>>> >>>> Have other people run into this problem? Are there solution options >>>> I'm missing? What option have you chosen? >>>> >>>> Thank you! >>>> Dima >>>> >>> >>> >>> -- >>> Best Regards >>> >>> Jeff Zhang >>> >> > > -- > Best Regards > > Jeff Zhang >
