Re: notebook interpreter restart

Thanks a lot, we miss that setting, will do the experiments right away, :) best AL > On Jan 25, 2017, at 6:17 PM, Paul Brenner wrote: > > > Did you try setting your interpreter to “Isolated” mode? Is it currently in > “shared” mode? > > If you haven’t played with

Re: notebook interpreter restart

Did you try setting your interpreter to “Isolated” mode? Is it currently in “shared” mode?  If you haven’t played with this setting before then:  1. Open the interpreters page 2. Find your interpreter and click the edit button in the top right corner 3. Beneath the word “option” at the top

Re: notebook interpreter restart

Hello, Paul Thank you so much for prompt reply. Our understanding is each interpreter takes one application on YARN, if multiple notebooks share same interpreter will run through same YARN application. As you mentioned this “… which will kill any other YARN application associated with that

notebook interpreter restart

Alec, The way we use zeppelin at our company is to set our interpreters to “isolated”. That way each notebook gets it’s own application on yarn.  This mostly works well. The one downside is that if you stop a notebook (e.g. by calling sys.exit in a cell of a spark notebook) it does stop the

notebook interpreter restart

Hi, all Currently we are exploring feature of zeppelin, now the situation we are using YARN to manage spark jobs. In terms of the experiments, we conclude that one interpreter is corresponding to An application in YARN cluster, that means all the notebooks from zeppelin with same interpreter