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 >
