On 1/15/2018 8:00 AM, Atin Mukherjee wrote:
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.
Thank you Atin, that worked perfectly!
On glusterfs2, I edited the uuid file for glusterfs1 and changed the
state from 5 to 3, then restarted glusterd on glusterfs2.
On glusterfs1, I edited the uuid file for glusterfs2 and changed the
state from 5 to 3, then restarted glusterd on glusterfs1.
Now all three systems are reporting the proper peer status, and the
volume status is also now reporting properly, even after a reboot of the
servers.
Thank you!
-Dj
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
