I just did this last week from 3.3.0->3.4.2.
I never got the peer probe problems - but I did end up with 2 files being in a split-brain situation.
Note: I only had ~hundred files that are qcow2 for KVM, so 2 files getting split-brain is about 2% filesystem problem.I never got the peer probe problems - but I did end up with 2 files being in a split-brain situation.
On Tue, Mar 4, 2014 at 1:43 AM, João Pagaime <joao.pagaime@xxxxxxxxx> wrote:
Hello all
anyone tried a rolling upgrades with no downtime [1] from 3.3.0 to 3.4.2 or similar upgrade? any comments?
for testing purposes we've installed a 3.4.2 server and it won't peer, giving the error "peer probe: failed: Peer X does not support required op-version".
I guess this is expected behavior for a new entry on the cluster
What about changing the software on an existing peer of the cluster? Will it also refuse to re-enter the cluster after the upgrade for the same reason (peers not supporting the required op-version)?
After all servers and clients are upgraded, how to increase the op-version of the global cluster?
best regards,
joão
[1]
http://vbellur.wordpress.com/2013/07/15/upgrading-to-glusterfs-3-4/
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
