<div dir="ltr">Sorry not mentioning the version of glusterfs.<div>I am using glusterfs 3.4.2-2 and it is on debian 7.2</div><div><br></div><div>Cary</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 5, 2014 at 2:15 PM, James <span dir="ltr"><<a href="mailto:purpleidea@gmail.com" target="_blank">purpleidea@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, May 5, 2014 at 5:11 PM, Cary Tsai <<a href="mailto:f4lens@gmail.com">f4lens@gmail.com</a>> wrote:<br>
> I have 4 systems, us-east-1, us-east-2, us-west-1, and us-west-2.<br>
> From us-east-1, it sees us-east-2 state as : Accepted peer request<br>
> (Connected)<br>
> But other systems sees it as "Peer in Cluster (Connected)"<br>
><br>
> Due to us-east-2 is " Accepted peer request " I cannot create a volume<br>
> using brick in us-east-2 on us-east-1.<br>
><br>
> How do I make us-east-2 seen as "Peer in Cluster" in us-east-1?<br>
><br>
> Thanks<br>
<br>
This looks like bug: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1051992
Puppet-Gluster" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1051992<br>
Puppet-Gluster</a> [1] automatically detects this issue and works around it.<br>
You can restart glusterd on the affected host to workaround it too.<br>
Please comment on the bug with your information.<br>
<br>
HTH,<br>
James<br>
<br>
[1] <a href="https://github.com/purpleidea/puppet-gluster" target="_blank">https://github.com/purpleidea/puppet-gluster</a><br>
><br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> <a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div><br></div>