good job ! it seems to be very interesting 2018-07-18 7:30 GMT+02:00 liuxun <neliu...@163.com>:
> 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 diagram. > > > The email attachment exceeded the size limit, so I reorganized the > document and updated it with Google Docs. > https://docs.google.com/document/d/1a8QLSyR3M5AhlG1GIYuDTj6bwazeu > VDKCRRBm-Qa3Bw/edit?usp=sharing > > > 在 2018年7月18日，下午1:03，liuxun <neliu...@163.com> 写道： > > hi，Ruslan Dautkhanov > > Thank you very much for your question. according to your advice, I added 3 > schematics to illustrate. > 1. Zeppelin Cluster architecture diagram. > 2. Distributed zeppelin Server fault tolerance diagram. > 3. Distributed zeppelin Server & intp process fault tolerance diagram. > > Later, I will merge the schematic into the system design document. > > <Zeppelin system architecture diagram00.png> > > > <Distributed zeppelin Server fault tolerance diagram 1.png> > > > > <Distributed zeppelin Server fault tolerance diagram 2.png> > > > > 在 2018年7月18日，上午1:16，Ruslan Dautkhanov <dautkha...@gmail.com> 写道： > > 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 to a survived > instance? > > Thanks, > Ruslan Dautkhanov > > > On Tue, Jul 17, 2018 at 2:46 AM liuxun <neliu...@163.com> wrote: > > hi: > > Our company installed and deployed a lot of zeppelin for data analysis. > The single server version of zeppelin could not meet our application > scenarios, so we transformed zeppelin into a clustered service that > supports distributed deployment, Have a unified entrance, high > availability, and High server resource usage. the email attachment is the > entire design document, I am very happy to feedback our modified code back > to the community. > > > this is the JIRA I submitted in the community, > > https://issues.apache.org/jira/browse/ZEPPELIN-3471 > > > Since the design document size exceeds the mail attachment size limit, the > document link address has to be sent. > > https://issues.apache.org/jira/secure/attachment/12931896/Zeppelin% > 20distributed%20architecture%20design.pdf > > https://issues.apache.org/jira/secure/attachment/ > 12931895/zepplin%20Cluster%20Sequence%20Diagram.png > > > liuxun > > > >
