Re: [Gluster-users] Proposal for GlusterD-2.0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




----- Original Message -----
> > As part of the first phase, we aim to delegate the distributed
> > configuration
> > store. We are exploring consul [1] as a replacement for the existing
> > distributed configuration store (sum total of /var/lib/glusterd/* across
> > all
> > nodes). Consul provides distributed configuration store which is consistent
> > and partition tolerant. By moving all Gluster related configuration
> > information into consul we could avoid split-brain situations.
> 
> Overall, I like the idea.  But I think you knew that.  ;)

Thanks. I am glad you like it :-)
> 
> Is the idea to run consul on all nodes as we do with glusterd, or to run
> it only on a few nodes (similar to Ceph's mon cluster) and then use them
> to coordinate membership etc. for the rest?

It is not set in stone, but I think we should have consul running only on
a subset of the nodes in the cluster, similar to Ceph's mon cluster approach.

~KP

> _______________________________________________
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
> 
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux