helix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kishore g <g.kish...@gmail.com>
Subject Re: Self managed cluster
Date Sat, 23 Feb 2013 04:06:49 GMT
I dint get the requirement. Do you have only two nodes and you want one of
them to be master and other to be slave?

What do you mean one of them will setup Helix cluster, Why cant you create
the cluster upfront? will there be more nodes in this cluster ?

two node zookeeper is not of much use. If one zookeeper node dies,then
there wont be a quorum and service will be down.

On Fri, Feb 22, 2013 at 6:07 PM, Ming Fang <mingfang@mac.com> wrote:

> Hi
> I am looking for feasibility advice on building a self managed cluster.
> Basically I don't have to have to maintain a separate Zookeeper and/or
> Controller processes.
> If I have a Master and a Slave, each will embed a Zookeeper node, forming
> a Zookeeper cluster.
> Then one of them will setup the Helix cluster.
> This can be done by first creating global Zookeeper lock before setting up
> the cluster if it does already exist.
> It doesn't look like Helix supports distribute locks, but it's not hard to
> do.
> The biggest problem I see in this is that with even number of nodes,
> Zookeeper can no form a quorum and that can result in split brain.
> Do you see any other problems with this design?
> Thanks
> --ming

View raw message