Basically active-(hot)standby model would work.
Two or more Zeppelin instance can be started and pointing the same notebook
storage, if only one Zeppelin instance (active) change notebook at any
given time.

In case of the active instance fails, one of rest instance can take over
the role by refreshing notebook list and start make change.

But all these fail over is not provided by Zeppelin and need to depends on
external script or HA software (like Heartbeat).

Like Jeff mentioned, community does not have concrete plan for having HA
built-in at this moment.

Hope this helps,

Thanks,
moon

On Fri, Jun 30, 2017 at 1:01 PM Jeff Zhang <zjf...@gmail.com> wrote:

>
> No concrete plan for that. There're other higher priority things need to
> be done. At least it would not be available in 0.8, maybe after 1.0
>
>
> wenxing zheng <wenxing.zh...@gmail.com>于2017年6月30日周五 上午11:47写道:
>
>> Thanks to Jianfeng.
>>
>> Do you  know any plan on this?
>>
>>
>> On Fri, Jun 30, 2017 at 11:32 AM, Jianfeng (Jeff) Zhang <
>> jzh...@hortonworks.com> wrote:
>>
>>> HA is not supported, there’s still  lots of configuration files stored
>>> in local file system.
>>>
>>>
>>>
>>> Best Regard,
>>> Jeff Zhang
>>>
>>>
>>> From: wenxing zheng <wenxing.zh...@gmail.com>
>>> Reply-To: "users@zeppelin.apache.org" <users@zeppelin.apache.org>
>>> Date: Friday, June 30, 2017 at 9:40 AM
>>> To: "users@zeppelin.apache.org" <users@zeppelin.apache.org>
>>> Subject: Query about the high availability of Zeppelin
>>>
>>> Hello all,
>>>
>>> I still didn't find any docs on this topic? Appreciated if anyone can
>>> shed some lights on how to get the Zeppelin into a cluster with
>>> shared/centralized storage
>>>
>>> Regards, Wenxing
>>>
>>
>>

Reply via email to