Re: Zeppelin distributed architecture design

2018-07-18 Thread vincent gromakowski
good job ! it seems to be very interesting 2018-07-18 7:30 GMT+02:00 liuxun : > hi,Ruslan Dautkhanov > > Thank you very much for your question. according to your advice, I added 3 > schematics to illustrate. > 1. Distributed Zeppelin Deployment architecture diagram. > 2. Distributed zeppelin Serv

Re: multi-tennant Zeppelin notebook

2016-11-29 Thread vincent gromakowski
eate one? > > Thanks, > moon > > [1] http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/ > manual/userimpersonation.html > [2] https://github.com/apache/zeppelin/pull/1672 > > > On Tue, Nov 29, 2016 at 11:05 AM vincent gromakowski < > vincent.gromakow...@gmail.com>

Re: multi-tennant Zeppelin notebook

2016-11-29 Thread vincent gromakowski
It bas been asked many times. For now only livy can impersonate the spark user. For other interpreters it's not possible as I know... Le 29 nov. 2016 7:44 PM, "Ruslan Dautkhanov" a écrit : > What's a best way to have a multi-tennant Zeppelin notebook? > > It seems we currently will have to ask u

Re: Sharing RDDS across applications and users

2016-10-28 Thread vincent gromakowski
Bad idea. No caching, cluster over consumption... Have a look on instantiating a custom thriftserver on temp tables with fair scheduler to allow concurrent SQL requests. It's not a public API but you can find some examples. Le 28 oct. 2016 11:12 AM, "Mich Talebzadeh" a écrit : > Hi, > > I think

Re: Sharing RDDS across applications and users

2016-10-27 Thread vincent gromakowski
Hi Just point all users on the same app with a common spark context. For instance akka http receives queries from user and launch concurrent spark SQL queries in different actor thread. The only prerequsite is to launch the different jobs in different threads (like with actors). Be carefull it's no

Re: Sharing RDDS across applications and users

2016-10-27 Thread vincent gromakowski
a or any other property which may arise > from relying on this email's technical content is explicitly disclaimed. > The author will in no case be liable for any monetary damages arising from > such loss, damage or destruction. > > > > On 27 October 2016 at 12:27, vincent gr

Re: Sharing RDDS across applications and users

2016-10-27 Thread vincent gromakowski
ead safe RDD sharing between spark jobs ==> these are best for sharing between users 2016-10-27 12:59 GMT+02:00 vincent gromakowski < vincent.gromakow...@gmail.com>: > I would prefer sharing the spark context and using FAIR scheduler for > user concurrency > > Le 27 oct. 2016 12

Re: Sharing RDDS across applications and users

2016-10-27 Thread vincent gromakowski
t at your own risk. Any and all responsibility for any > loss, damage or destruction of data or any other property which may arise > from relying on this email's technical content is explicitly disclaimed. > The author will in no case be liable for any monetary damages arising

Re: Sharing RDDS across applications and users

2016-10-27 Thread vincent gromakowski
Ignite works only with spark 1.5 Ignite leverage indexes Alluxio provides tiering Alluxio easily integrates with underlying FS Le 27 oct. 2016 12:39 PM, "Mich Talebzadeh" a écrit : > Thanks Chanh, > > Can it share RDDs. > > Personally I have not used either Alluxio or Ignite. > > >1. Are the

Re: zeppelin with spark 2.0.1

2016-10-13 Thread vincent gromakowski
d. > The author will in no case be liable for any monetary damages arising from > such loss, damage or destruction. > > > > On 13 October 2016 at 08:44, vincent gromakowski < > vincent.gromakow...@gmail.com> wrote: > >> In this case it works with spark included

Re: zeppelin with spark 2.0.1

2016-10-13 Thread vincent gromakowski
n of data or any other property which may arise from relying on this email's technical content is explicitly disclaimed. The author will in no case be liable for any monetary damages arising from such loss, damage or destruction. On 13 October 2016 at 08:38, vincent gromakowski < vince

Re: zeppelin with spark 2.0.1

2016-10-13 Thread vincent gromakowski
> loss, damage or destruction of data or any other property which may arise > from relying on this email's technical content is explicitly disclaimed. > The author will in no case be liable for any monetary damages arising from > such loss, damage or destruction. > > > >

zeppelin with spark 2.0.1

2016-10-12 Thread vincent gromakowski
Hi all, I am trying to configure zeppelin for spark 2.0.1 but when I precise the SPARK_HOME in zeppelin-env.sh I get this error java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketIm

Re: zeppelin architecture with multiple users

2016-09-22 Thread vincent gromakowski
2016-09-22 10:12 GMT+02:00 vincent gromakowski < vincent.gromakow...@gmail.com>: > Hi, > From my point of view you have 3 options: > > 1. Use a dedicated zeppelin instance per user. Solution I currently use. > Mesos/marathon launch an instance by user with it's linu

Re: zeppelin architecture with multiple users

2016-09-22 Thread vincent gromakowski
Hi, >From my point of view you have 3 options: 1. Use a dedicated zeppelin instance per user. Solution I currently use. Mesos/marathon launch an instance by user with it's linux UID. A service discovery is routing each user based on HTTPS basic auth to his instance. Because the configuration file

Re: zeppelin build error

2016-08-07 Thread vincent gromakowski
Hi You were right, build success without -Pr thanks 2016-08-06 17:18 GMT+02:00 moon soo Lee : > Hi, > > Could you try include "-Psparkr" but not "-Pr" ? > "-Pr" is not tested with spark-2.0 and scala-2.11. > > Thanks, > moon > &

zeppelin build error

2016-08-06 Thread vincent gromakowski
Hi all, I have the following error trying to build Zeppelin from source with this command mvn -X clean package -Pbuild-distr -Pspark-2.0 -Phadoop-2.6 -Ppyspark -Psparkr -Pscala-2.11 -Pr -DskipTests [ERROR] Failed to execute goal on project zeppelin-zrinterpreter_2.10: Could not resolve dependencie

Re: Multiuser support of Zeppelin.

2016-08-05 Thread vincent gromakowski
One zeppelin per user in mesos container on datanode type server is fine for me. An Ansible script configure each instance with user specifities and launch it in Marathon. A service discovery (basic shell script) update an apache server with basic auth and route each user to his instance. Mesos als

Re: Zeppelin multi-user dashboards

2016-06-16 Thread vincent gromakowski
Isnt it acheivable via git repository ? A kind of git clone to get an indépendant copy of the notebook? Le 17 juin 2016 4:18 AM, "Corneau Damien" a écrit : > It is simple Read/Write > Some people can edit, some people can see. > > By essence, if the view is different from each user, then it is no