<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">hello Bryan and thanks for sharing!<br>
<br>
how did you fix those 2 files on a split-brain situation? deleted
one "bad" file?
<div id="gt-src-tools">
<div id="gt-src-tools-l">
<div style="display: inline-block;" id="gt-input-tool">
<div id="itamenu"><span class="ita-kd-inputtools-div"></span></div>
</div>
</div>
</div>
<div id="gt-res-content" class="almost_half_cell">
<div dir="ltr" style="zoom:1">
<div id="tts_button" style="" class=""><object
type="application/x-shockwave-flash"
data="//ssl.gstatic.com/translate/sound_player2.swf"
id="tts" width="18" height="18"></object><span
id="result_box" class="short_text" lang="en"><span
class="hps"> which</span></span> one to select for
deletion?<br>
<br>
on an software update situation I would expect not to have
peer probe problems, simply because there are no "gluster
peer probe" commands. The problem that could happen is the
updated 3.4.2 node having problems reentering a 3.3.0
cluster (without "peer probes" commands). It's good news it
went well<br>
<br>
best regards<br>
joao<br>
</div>
</div>
</div>
<br>
Em 04-03-2014 18:30, Bryan Whitehead escreveu:<br>
</div>
<blockquote
cite="mid:CAA3XVTw+15Hd4SrwLKZ5-oxdc4+4TNzfAS1DNS9f69wz34qeAg@mail.gmail.com"
type="cite">
<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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="http://vbellur.wordpress.com/2013/07/15/upgrading-to-glusterfs-3-4/"
target="_blank">http://vbellur.wordpress.com/2013/07/15/upgrading-to-glusterfs-3-4/</a><br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a moz-do-not-send="true"
href="http://supercolony.gluster.org/mailman/listinfo/gluster-users"
target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>