Hi All, I’m running GlusterFS on a cluster hosted in AWS. I have a script which provisions my instances and thus will set up GlusterFS (specifically: glusterfs 3.5.8).
root@ip-xx-xx-xx-1:/home/ubuntu# gluster peer status Number of Peers: 3 Hostname: xx.xx.xx.2 Uuid: 3b4c1fb9-b325-4204-98fd-2eb739fa867f State: Peer in Cluster (Connected) Hostname: xx.xx.xx.3 Uuid: acfc1794-9080-4eb0-8f69-3abe78bbee16 State: Sent and Received peer request (Connected) Hostname: xx.xx.xx.4 Uuid: af33463d-1b32-4ffb-a4f0-46ce16151e2f State: Peer in Cluster (Connected) Running gluster peer status on the instance that is affected yields: root@ip-xx-xx-xx-3:/var/log/glusterfs# gluster peer status Hostname: xx.xx.xx.1 Uuid: c4f17e9a-893b-48f0-a014-1a05cca09d01 State: Peer is connected and Accepted (Connected) Of which the status (Connected) in this case, will fluctuate between ‘Connected’ and ‘Disconnected’. I have been unable to locate the cause of this issue. Has this been encountered before, and if so is there a general fix? I haven’t been able to find anything as of yet. Many thanks, Tommy |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users