So that is concerning the drivers, which clearly have to fit on one single
machine. But what about the Zeppelin server service itself? Any bottlenecks for
how many concurrent drivers processes it can handle?
-
René Pfitzner
Lead Data Scientists
Neue Zürcher Zeitung
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
I’m using the plotting features of the table display system. I’m using the
postgres/psql interpreter. I noticed a few issues and I’m hoping that someone
can point me in the right direction to resolve these issues:
1) I’m unable to display a value on y-axis (number field) as is (it forces me
to
Hi Moon,
I believe there are many use cases beyound our needs, when users could
access
rest API directly through 'z' variable.
Done: https://issues.apache.org/jira/browse/ZEPPELIN-1814
Thank you.
--
Ruslan Dautkhanov
On Wed, Dec 14, 2016 at 8:53 AM, moon wrote:
> Hi Ruslan,
>
> Although y
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) interpreter
