<div dir="ltr"><div><br>Currently I'm with IBM Lab Services, and only have small test clusters myself. <br><br>I'm not sure I've done v3.5->4.1 upgrades, but this warning<br></div><div> about upgrading all nodes within a "short time" is something that's always been in the upgrade instructions, and I've been through many of these (I've been a gpfs sysadmin since 2002 :-)<br><br> <a href="http://www.ibm.com/support/knowledgecenter/SSFKCN_3.5.0/com.ibm.cluster.gpfs.v3r5.gpfs300.doc/bl1ins_migratl.htm">http://www.ibm.com/support/knowledgecenter/SSFKCN_3.5.0/com.ibm.cluster.gpfs.v3r5.gpfs300.doc/bl1ins_migratl.htm</a><br> <a href="https://www.scribd.com/document/51036833/GPFS-V3-4-Concepts-Planning-and-Installation-Guide" dir="ltr">https://www.scribd.com/document/51036833/GPFS-V3-4-Concepts-Planning-and-Installation-Guide</a><br><br>BTW: One relevant issue I saw recently was a rolling upgrade from 4.1.0 to 4.1.1.7 where we had some nodes in the cluster running 4.1.0.0. Apparently there had been some CCR message format changes in a later release that made 4.1.0.0-nodes not being able to properly communicate with 4.1.1.4 -- even though they should be able to co-exist in the same cluster according to the upgrade instructions. So I guess the more versions you mix in a cluster, the more likely you're to hit a version mismatch bug. Best to feel a tiny bit uneasy about not running same version on all nodes, and hurry to get them all upgraded to the same level. And also, should you hit a bug during this process, the likely answer will be to upgrade everything to same level.<br><br><br><br></div><div> -jf<br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 6, 2016 at 12:00 AM, Aaron Knister <span dir="ltr"><<a href="mailto:aaron.s.knister@nasa.gov" target="_blank">aaron.s.knister@nasa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks Jan-Frode! If you don't mind sharing, over what period of time did you upgrade from 3.5 to 4.1 and roughly how many clients/servers do you have in your cluster?<br>
<br>
-Aaron<span class=""><br>
<br>
On 12/5/16 5:52 PM, Jan-Frode Myklebust wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
I read it as "do your best". I doubt there can be problems that shows up<br>
after 3 weeks, that wouldn't also be triggerable after 1 day.<br>
<br>
<br>
-jf<br>
<br>
man. 5. des. 2016 kl. 22.32 skrev Aaron Knister<br></span>
<<a href="mailto:aaron.s.knister@nasa.gov" target="_blank">aaron.s.knister@nasa.gov</a> <mailto:<a href="mailto:aaron.s.knister@nasa.gov" target="_blank">aaron.s.knister@nasa.g<wbr>ov</a>>>:<div><div class="h5"><br>
<br>
Hi Everyone,<br>
<br>
In the GPFS documentation<br>
(<a href="http://www.ibm.com/support/knowledgecenter/SSFKCN_4.1.0/com.ibm.cluster.gpfs.v4r1.gpfs300.doc/bl1ins_migratl.htm" rel="noreferrer" target="_blank">http://www.ibm.com/support/kn<wbr>owledgecenter/SSFKCN_4.1.0/com<wbr>.ibm.cluster.gpfs.v4r1.gpfs300<wbr>.doc/bl1ins_migratl.htm</a>)<br>
it has this to say about the duration of an upgrade from 3.5 to 4.1:<br>
<br>
> Rolling upgrades allow you to install new GPFS code one node at a time without shutting down GPFS<br>
> on other nodes. However, you must upgrade all nodes within a short time. The time dependency exists<br>
>because some GPFS 4.1 features become available on each node as soon as<br>
the node is upgraded, while<br>
>other features will not become available until you upgrade all<br>
participating nodes.<br>
<br>
Does anyone have a feel for what "a short time" means? I'm looking to<br>
upgrade from 3.5.0.31 to 4.1.1.10 in a rolling fashion but given the<br>
size of our system it might take several weeks to complete. Seeing this<br>
language concerns me that after some period of time something bad is<br>
going to happen, but I don't know what that period of time is.<br>
<br>
Also, if anyone has done a rolling 3.5 to 4.1 upgrade and has any<br>
anecdotes they'd like to share, I would like to hear them.<br>
<br>
Thanks!<br>
<br>
-Aaron<br>
<br>
--<br>
Aaron Knister<br>
NASA Center for Climate Simulation (Code 606.2)<br>
Goddard Space Flight Center<br>
<a href="tel:%28301%29%20286-2776" value="+13012862776" target="_blank">(301) 286-2776</a><br>
______________________________<wbr>_________________<br>
gpfsug-discuss mailing list<br></div></div>
gpfsug-discuss at <a href="http://spectrumscale.org" rel="noreferrer" target="_blank">spectrumscale.org</a> <<a href="http://spectrumscale.org" rel="noreferrer" target="_blank">http://spectrumscale.org</a>><br>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" rel="noreferrer" target="_blank">http://gpfsug.org/mailman/list<wbr>info/gpfsug-discuss</a><span class=""><br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at <a href="http://spectrumscale.org" rel="noreferrer" target="_blank">spectrumscale.org</a><br>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" rel="noreferrer" target="_blank">http://gpfsug.org/mailman/list<wbr>info/gpfsug-discuss</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
-- <br>
Aaron Knister<br>
NASA Center for Climate Simulation (Code 606.2)<br>
Goddard Space Flight Center<br>
<a href="tel:%28301%29%20286-2776" value="+13012862776" target="_blank">(301) 286-2776</a><br>
______________________________<wbr>_________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at <a href="http://spectrumscale.org" rel="noreferrer" target="_blank">spectrumscale.org</a><br>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" rel="noreferrer" target="_blank">http://gpfsug.org/mailman/list<wbr>info/gpfsug-discuss</a><br>
</div></div></blockquote></div><br></div>