I read it as "do your best". I doubt there can be problems that shows up after 3 weeks, that wouldn't also be triggerable after 1 day.
-jf man. 5. des. 2016 kl. 22.32 skrev Aaron Knister <[email protected]>: > Hi Everyone, > > In the GPFS documentation > ( > http://www.ibm.com/support/knowledgecenter/SSFKCN_4.1.0/com.ibm.cluster.gpfs.v4r1.gpfs300.doc/bl1ins_migratl.htm > ) > it has this to say about the duration of an upgrade from 3.5 to 4.1: > > > Rolling upgrades allow you to install new GPFS code one node at a time > without shutting down GPFS > > on other nodes. However, you must upgrade all nodes within a short time. > The time dependency exists > >because some GPFS 4.1 features become available on each node as soon as > the node is upgraded, while > >other features will not become available until you upgrade all > participating nodes. > > Does anyone have a feel for what "a short time" means? I'm looking to > upgrade from 3.5.0.31 to 4.1.1.10 in a rolling fashion but given the > size of our system it might take several weeks to complete. Seeing this > language concerns me that after some period of time something bad is > going to happen, but I don't know what that period of time is. > > Also, if anyone has done a rolling 3.5 to 4.1 upgrade and has any > anecdotes they'd like to share, I would like to hear them. > > Thanks! > > -Aaron > > -- > Aaron Knister > NASA Center for Climate Simulation (Code 606.2) > Goddard Space Flight Center > (301) 286-2776 > _______________________________________________ > gpfsug-discuss mailing list > gpfsug-discuss at spectrumscale.org > http://gpfsug.org/mailman/listinfo/gpfsug-discuss >
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
