[Gluster-users] Sent and Received peer request (Connected)

Dj Merrill gluster at deej.net
Thu Jan 11 19:54:53 UTC 2018


This morning I did a rolling update from the latest 3.7.x to 3.12.4,
with no client activity.  "Rolling" as in, shut down the Gluster
services on the first server, update, reboot, wait until up and running,
proceed to the next server.  I anticipated that a 3.12 server might not
properly talk to a 3.7 server but since I had no client activity I was
not overly concerned.

All three servers are now updated to 3.12.4.  The weirdness is that
although the third server reports a proper peer status of "Peer in
Cluster (Connected)" to both server 1 and 2, the first and second
servers report to each other "Sent and Received peer request
(Connected)" but show the proper "Peer in Cluster (Connected)" to the
third server.


[root at glusterfs1]# gluster peer status
Number of Peers: 2

Hostname: glusterfs2
Uuid: 0f4867d9-7be3-4dbc-83f6-ddcda58df607
State: Sent and Received peer request (Connected)

Hostname: glusterfs3
Uuid: 354fdb76-1205-4a5c-b335-66f2ee3e665f
State: Peer in Cluster (Connected)



[root at glusterfs2]# gluster peer status
Number of Peers: 2

Hostname: glusterfs3
Uuid: 354fdb76-1205-4a5c-b335-66f2ee3e665f
State: Peer in Cluster (Connected)

Hostname: glusterfs1
Uuid: 339533fd-5820-4077-a2a0-d39d21379960
State: Sent and Received peer request (Connected)



[root at glusterfs3]# gluster peer status
Number of Peers: 2

Hostname: glusterfs2
Uuid: 0f4867d9-7be3-4dbc-83f6-ddcda58df607
State: Peer in Cluster (Connected)

Hostname: glusterfs1
Uuid: 339533fd-5820-4077-a2a0-d39d21379960
State: Peer in Cluster (Connected)


In my notes I have a procedure for Rejected peers, which I tried:

   Stop glusterd (systemctl stop glusterd)
   In /var/lib/glusterd, delete everything except glusterd.info (the
UUID file)
   Start glusterd (systemctl start glusterd)
   Probe one of the good peers (gluster peer probe HOSTNAME), then probe
the second
   Restart glusterd, check 'gluster peer status'

This hasn't changed anything.  I've tried reboots of all servers, etc.


Any thoughts on how to correct this?

Thanks,

-Dj


More information about the Gluster-users mailing list