> On Mar 7, 2018, at 4:39 AM, Atin Mukherjee <amukh...@redhat.com> wrote:
> Please run 'gluster v get all cluster.max-op-version' and what ever value it
> throws up should be used to bump up the cluster.op-version (gluster v set all
> cluster.op-version <value>) . With that if you restart the rejected peer I
> believe the problem should go away, if it doesn't I'd need to investigate
> further once you can pass down the glusterd and cmd_history log files and the
> content of /var/lib/glusterd from all the nodes.
Thanks so much - that worked.
I clearly need to catch up on my Gluster reading - I thought I understood
op-version, but clearly don't.
Anyway, thanks again for putting up with me.
Gluster-users mailing list