Hello,
After verifying that our backup was good we tried upgrading the other
server to version 9.6, and then it worked fine. So it appears that version
9.1 and 9.6 couldn't talk to each other.
Is this expected? I had thought that nodes with the same major version
number would be able to
Hi Eli,
Thanks for the response. I had hoped for a simple fix here, but I think
perhaps there isn't one. I have built this as a part of a new environment,
eventually replacing a much older system built with Gluster 3.10 (yes -
that old). I appreciate the warning about 10.3 and will run some
I've seen issues with symlinks failing to heal as well. I never found
a good solution on the glusterfs side of things. Most reliable fix I
found is just rm and recreate the symlink in the fuse volume itself.
Also, I'd strongly suggest heavy load testing before upgrading to 10.3
in production,
Just upgraded my test 3 node distributed-replica 9x2 glusterfs to 11.0
and it was a bit rough. After upgrading the 1st node, gluster volume
status showed only the bricks on node 1, and gluster peer status
showed node1 rejecting node 2 & 3. After upgrading node2, and then
node3, node 3 remained
Hi David,
It seems like a network issue to me, As it's unable to connect the other node
and getting timeout.
Few things you can check-
* Check the /etc/hosts file on both the servers and make sure it has the
correct IP of the other node.
* Are you binding gluster on any specific IP,
