[Gluster-devel] Proposal for GlusterD-2.0
jdarcy at redhat.com
Fri Sep 5 12:28:23 UTC 2014
> As part of the first phase, we aim to delegate the distributed configuration
> store. We are exploring consul  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. ;)
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?
More information about the Gluster-devel