Yes, this would be a critical performance issue for multiple user case. Because currently zeppelin only support yarn-client mode which means the driver JVM is in the same host of zeppelin server. So regarding the concurrent users, it depends on the memory you configure for the driver and how many memory you have for the machine.
But for the long term, we should support yarn-cluster mode. Here¹s one ticket and wiki for this https://issues.apache.org/jira/browse/ZEPPELIN-1377 https://cwiki.apache.org/confluence/display/ZEPPELIN/Cluster+Manager+Propos al Best Regard, Jeff Zhang On 12/14/16, 11:27 PM, "blaubaer" <rene.pfitz...@nzz.ch> wrote: >Hi > >We are running Zeppelin (0.5) on our YARN managed cluster. To allow for >multiple concurrent users, without sharing the spark context, we simply >setup one interpreter for every user. This works pretty OK, however, at >some >point we seem to hit the limit of how many concurrent (spark) interpreters >the Zeppelin (daemon) service can handle. Now with the ³new² (0.6) feature >of isolated notebooks, this topic should pop up with other users as well. > >So, I was wondering: what are your experiences with multiple concurrent >interpreters? What are determining factors for the question how many >concurrent interpreters can run (besides from cluster resources to >actually >be able to start the multiple interpreters)? Any experiences on that? For >us >it seems that 2-3 is OK, 4-5 get¹s critical, but that also depends on the >load of the jobs it seems. > >Thx. > > > >-- >View this message in context: >http://apache-zeppelin-users-incubating-mailing-list.75479.x6.nabble.com/L >imit-on-multiple-concurrent-interpreters-isolated-notebooks-tp4732.html >Sent from the Apache Zeppelin Users (incubating) mailing list mailing >list archive at Nabble.com. >
