<html><body><div style="font-family: Arial; font-size: 10pt; color: #000000"><div>Yeah I'll be doing a test upgrade and migration to make sure it works in the lap but my production stuff significantly more busy so we'll see if it folds under pressure. My biggest concern is when I'll have one node 3.5.2 and one node 3.6.3 in a replica set. I don't see any major reason why they wouldn't be compatible or cause data issues but I thought I would check with the list first. </div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Pranith Kumar Karampuri" <pkarampu@redhat.com><br><b>To: </b>"Josh Boon" <gluster@joshboon.com>, "Gluster-users@gluster.org List" <gluster-users@gluster.org><br><b>Sent: </b>Tuesday, May 5, 2015 12:55:19 AM<br><b>Subject: </b>Re: [Gluster-users] Gluster 3.5.2 upgrade to Gluster 3.6.3 QEMU gfafpi complications<br><div><br></div>
<br>
<div class="moz-cite-prefix">On 05/05/2015 02:27 AM, Josh Boon
wrote:<br>
</div>
<blockquote cite="mid:1338701210.836456.1430773033847.JavaMail.zimbra@80ok.be">
<div style="font-family: Arial; font-size: 10pt; color: #000000">
<div>Hey folks,</div>
<div><br>
</div>
<div>I'll be doing an upgrade soon for my core hypervisors
running qemu 2.0 built with Gluster 3.5.2 connecting to a
replicated 3.5.2 volume.</div>
<div><span style="font-size: 10pt;">The upgrade path I'd like to
do is:</span></div>
<div><span style="font-size: 10pt;">1. migrate all machines to
node not being upgraded</span></div>
<div><span style="font-size: 10pt;">2. prevent client heals as
documented over
at <a class="moz-txt-link-freetext" href="http://www.gluster.org/community/documentation/index.php/Upgrade_to_3.6" target="_blank">http://www.gluster.org/community/documentation/index.php/Upgrade_to_3.6</a></span></div>
<div><span style="font-size: 10pt;">3. stop gluster server and
gluster processes on node being upgraded </span></div>
<div><span style="font-size: 10pt;">4. upgrade kvm, gluster, and
supporting packages to required to 3.6.3</span></div>
<div><span style="font-size: 10pt;">5. restart node being
upgraded</span></div>
<div><span style="font-size: 10pt;">6. Node joins pool again
except one node will be running 3.6.3 and the other 3.5.2</span></div>
<div><span style="font-size: 10pt;">7. perform heal to ensure
data correct</span></div>
<div><span style="font-size: 10pt;">8. migrate all machines over
to newly upgraded node</span></div>
<div><span style="font-size: 10pt;">9. repeat steps 3-5 for
other node</span></div>
<div><span style="font-size: 10pt;">10. perform heal to ensure
data correct</span></div>
<div><span style="font-size: 10pt;">11. rebalance machines as
necessary</span></div>
<div><span style="font-size: 10pt;">12. upgrade complete</span></div>
<div><span style="font-size: 10pt;"><br>
</span></div>
<div><span style="font-size: 10pt;">This method has the obvious
issue of will the two nodes behave as expected when on
different major versions with the gain of no downtime for
vm's. Is this method too risky? Has anyone tried it? Would
appreciate any input.</span></div>
</div>
</blockquote>
One way to gain confidence is to perform this on a test setup to
know more about how your workload is affected by this upgrade?<br>
<br>
Pranith<br>
<blockquote cite="mid:1338701210.836456.1430773033847.JavaMail.zimbra@80ok.be">
<div style="font-family: Arial; font-size: 10pt; color: #000000">
<div><span style="font-size: 10pt;"><br>
</span></div>
<div><span style="font-size: 10pt;">Thanks,</span></div>
<div><span style="font-size: 10pt;">Josh</span></div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</div><div><br></div></div></body></html>