I have the same issue. We might need to investigate it deeply. Could you
please file it up?
Regards,
JL
On Tue, Jul 17, 2018 at 7:27 PM, Chris Penny wrote:
> Hi all,
>
> Thanks for the 0.8.0 release!
>
> We’re keen to take advantage of the yarn-cluster support to take the
> pressure off our
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
I created ZEPPELIN-3635 for dropping support before spark 1.6, if you have
any concerns, please comment on that jira.
Clemens Valiente 于2018年7月17日周二 下午4:05写道：
> As far as I know, the Cloudera distribution of hadoop still comes with
> Spark 1.6 out of the box, so I believe there are still quite
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
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
Ability to work with many data source is one the reason we chose Apache
Zeppelin.
For branch-0.7 our ops-team wrote a lot of python functions for import and
export data from diffent source (Greenlum, Hive, Oracle) using Python DataFrame
as middleware.
Our users can upload flat files to
Hi all,
Thanks for the 0.8.0 release!
We’re keen to take advantage of the yarn-cluster support to take the
pressure off our Zeppelin host. However, I am having some trouble with it.
The first problem was in following the documentation here:
