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/ and then restart
the glusterd service.
Thank you Atin, that worked perfectly!
On glusterfs2, I edited the uuid file for glusterfs1 an
On Fri, 12 Jan 2018 at 01:34, Dj Merrill wrote:
> 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 ant
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
