Hello,
We have a production system with around 50GB of data running GlusterFS
5.13. It has 3 replicating/mirrored nodes, and also geo-replicates to
another site.
How safe would it be to upgrade to a more recent major version, eg 7.x? I'm
not sure how recommended in-place upgrades are, or if a
Hello,
We're having an issue with the rotated gsyncd.log not being released.
Here's the output of 'lsof':
# lsof | grep 'gsyncd.log.1'
python24495 root3w REG8,1
9916750234332241
/var/log/glusterfs/geo-replication/gvol0_nvfs10_gvol0/gsyncd.log.1
Dear Nikhil,
Thank you for your answer. So does this mean that all my FUSE clients where I
have the volume mounted will not loose at any time their connection during the
whole upgrade procedure of all 3 nodes?
I am asking because if I understand correctly there will be an overlap of time
Il 21/08/20 13:56, Diego Zuccato ha scritto:
Hello again.
I also tried disabling bitrot (and re-enabling it afterwards) and the
procedure for recovery from split-brain[*] removing the file and its
link from one of the nodes, but no luck.
I'm now completely out of ideas :(
How can I resync
Hello Mabi
You don't need to follow the offline upgrade procedure. Please do follow
the online upgrade procedure only. Upgrade the nodes one by one, you will
notice the `Peer Rejected` state, after upgrading one node or so, but once
all the nodes are upgraded it will be back to `Peer in
