<div><br><div class="gmail_quote"><div dir="auto">On Fri, 12 Jan 2018 at 01:34, Dj Merrill <<a href="mailto:gluster@deej.net">gluster@deej.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This morning I did a rolling update from the latest 3.7.x to 3.12.4,<br>
with no client activity. "Rolling" as in, shut down the Gluster<br>
services on the first server, update, reboot, wait until up and running,<br>
proceed to the next server. I anticipated that a 3.12 server might not<br>
properly talk to a 3.7 server but since I had no client activity I was<br>
not overly concerned.<br>
<br>
All three servers are now updated to 3.12.4. The weirdness is that<br>
although the third server reports a proper peer status of "Peer in<br>
Cluster (Connected)" to both server 1 and 2, the first and second<br>
servers report to each other "Sent and Received peer request<br>
(Connected)" but show the proper "Peer in Cluster (Connected)" to the<br>
third server.<br>
<br>
<br>
[root@glusterfs1]# gluster peer status<br>
Number of Peers: 2<br>
<br>
Hostname: glusterfs2<br>
Uuid: 0f4867d9-7be3-4dbc-83f6-ddcda58df607<br>
State: Sent and Received peer request (Connected)<br>
<br>
Hostname: glusterfs3<br>
Uuid: 354fdb76-1205-4a5c-b335-66f2ee3e665f<br>
State: Peer in Cluster (Connected)<br>
<br>
<br>
<br>
[root@glusterfs2]# gluster peer status<br>
Number of Peers: 2<br>
<br>
Hostname: glusterfs3<br>
Uuid: 354fdb76-1205-4a5c-b335-66f2ee3e665f<br>
State: Peer in Cluster (Connected)<br>
<br>
Hostname: glusterfs1<br>
Uuid: 339533fd-5820-4077-a2a0-d39d21379960<br>
State: Sent and Received peer request (Connected)<br>
<br>
<br>
<br>
[root@glusterfs3]# gluster peer status<br>
Number of Peers: 2<br>
<br>
Hostname: glusterfs2<br>
Uuid: 0f4867d9-7be3-4dbc-83f6-ddcda58df607<br>
State: Peer in Cluster (Connected)<br>
<br>
Hostname: glusterfs1<br>
Uuid: 339533fd-5820-4077-a2a0-d39d21379960<br>
State: Peer in Cluster (Connected)<br>
<br>
<br>
In my notes I have a procedure for Rejected peers, which I tried:<br>
<br>
Stop glusterd (systemctl stop glusterd)<br>
In /var/lib/glusterd, delete everything except <a href="http://glusterd.info" rel="noreferrer" target="_blank">glusterd.info</a> (the<br>
UUID file)<br>
Start glusterd (systemctl start glusterd)<br>
Probe one of the good peers (gluster peer probe HOSTNAME), then probe<br>
the second<br>
Restart glusterd, check 'gluster peer status'<br>
<br>
This hasn't changed anything. I've tried reboots of all servers, etc.</blockquote><div dir="auto"><br></div><div dir="auto">What you’d need to do is to set ‘state=3’ for the peer which is not in connected state in /var/lib/glusterd/peers/<uuid file> and then restart the glusterd service.</div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
<br>
Any thoughts on how to correct this?<br>
<br>
Thanks,<br>
<br>
-Dj<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div></div><div dir="ltr">-- <br></div><div class="gmail_signature" data-smartmail="gmail_signature">- Atin (atinm)</div>