<div dir="ltr"><div>I just did this last week from 3.3.0->3.4.2.<br><br>I never got the peer probe problems - but I did end up with 2 files being in a split-brain situation.<br><br></div>Note: I only had ~hundred files that are qcow2 for KVM, so 2 files getting split-brain is about 2% filesystem problem.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 4, 2014 at 1:43 AM, Joćo Pagaime <span dir="ltr"><<a href="mailto:joao.pagaime@gmail.com" target="_blank">joao.pagaime@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello all<br>
<br>
anyone tried a rolling upgrades with no downtime [1] from 3.3.0 to 3.4.2 or similar upgrade? any comments?<br>
<br>
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".<br>
<br>
I guess this is expected behavior for a new entry on the cluster<br>
<br>
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)?<br>
<br>
After all servers and clients are upgraded, how to increase the op-version of the global cluster?<br>
<br>
best regards,<br>
joćo<br>
<br>
[1]<br>
<a href="http://vbellur.wordpress.com/2013/07/15/upgrading-to-glusterfs-3-4/" target="_blank">http://vbellur.wordpress.com/<u></u>2013/07/15/upgrading-to-<u></u>glusterfs-3-4/</a><br>
______________________________<u></u>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.<u></u>org/mailman/listinfo/gluster-<u></u>users</a><br>
</blockquote></div><br></div>