Re: Zeppelin distributed architecture design

hi， I have submitted the first module of the zeppline cluster upgrade, please help me review the code, thank you! https://github.com/apache/zeppelin/pull/3156 I updated the atomix algorithm library module in the system design documentation, please

Re: Zeppelin distributed architecture design

hi， After 2 weeks of development, I have completed the development of upgrading copycat to the atomix algorithm library. The reason for the increased workload is the need to resolve the problem of netty package conflicts. Now it has been used on our intra-company clusters using the atomix algor

Re: Zeppelin distributed architecture design

Thank you. I fully agree with you that we need a framework to support distributed version. IMHO, we cannot afford to develop our own. I'll dig into atomix as well. On Tue, Jul 24, 2018 at 1:57 PM, liuxun wrote: > @Jongyoul Lee： > Thank you for your attention. > > Indeed, as you said, the `Cop

Re: Zeppelin distributed architecture design

@Jongyoul Lee： Thank you for your attention. Indeed, as you said, the `Copycat` project has been closed and has been migrated to `https://github.com/atomix/atomix`. I also considered this issue during development. The main reason was that it was enough to realize Raft using `Copycat` at the tim

Re: Zeppelin distributed architecture design

First of all, thank you for your effort and contribution. I read it carefully today, and personally, it's a very nice feature and idea. Let's discuss it and improve more concretely. I also left comments on the doc. And I have a simple question. `Copycat`, which you used to implement it, is depr

Re: Zeppelin distributed architecture design

HI： In order to more intuitively express the actual use of distributed zeppelin clusters. I updated this design document, starting with the 16th page of the document, adding 2 GIF animations showing the operation record screen of the zeppelin cluster we are using now. https://docs.google.com/do

Re: Zeppelin distributed architecture design

Thank you luxun, I left a couple of comments in that google document. -- Ruslan Dautkhanov On Tue, Jul 17, 2018 at 11:30 PM liuxun wrote: > hi，Ruslan Dautkhanov > > Thank you very much for your question. according to your advice, I added 3 > schematics to illustrate. > 1. Distributed Zeppeli

Re: Zeppelin distributed architecture design

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: Zeppelin distributed architecture design

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 Server fault tolerance diagram. 3. Distributed zeppelin Server & intp process fault tolerance

Re: Zeppelin distributed architecture design

Nice. Thanks for sharing. Can you explain how are users routed into a particular zeppelin server instance? I've seen nginx on top of them, but I don't think the document covers details? If one zeppelin server goes down or unhealthy, is nginx supposed to detect (if so, how?) that and reroute users