[Gluster-devel] Managing etcd (4.0)

Kaushal M kshlmster at gmail.com
Fri Sep 11 05:34:10 UTC 2015

One thing I read recently was that with etcd2, etcd nodes can operate
in something called a proxy mode (in either r/w or ro). Any new etcd
that joins the cluster after (IIRC) 9 automatically become a proxy
node. I'm trying to find the document/blog post/forum comment where I
read this.

On Thu, Sep 10, 2015 at 6:21 PM, Jeff Darcy <jdarcy at redhat.com> wrote:
>> I've a follow up question here. Could you elaborate the difference
>> between *use* & *join*?
> Venky's interpretation was the same as what I had intended.  "Join" means
> that the new node becomes both a server and client for the existing etcd
> cluster.  "Use" means that it becomes a client only, relinquishing its
> role as a server for its own (one-node) cluster.
>> consul/etcd documentation says that the ideal configuration is to have
>> 3-5 servers to form the cluster. The way I was thinking about it is
>> during peer probe we would check whether cluster has already gotten the
>> enough number of servers to form the cluster, if not then consider the
>> other end to join as a etcd server otherwise act as a client. Thoughts?
> We could do this automatically.  Good idea.  The one caveat is that,
> without topology information, we can't really do a good job ourselves of
> ensuring that the etcd servers are properly spread across racks (or
> switches or power supplies).  Maybe the option should be join/use/auto,
> with "auto" as the default but with potential for a user override.
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel

More information about the Gluster-devel mailing list