[lustre-discuss] Upgrading lustre servers
Spitz, Cory James
cory.spitz at hpe.com
Wed Feb 23 06:38:23 PST 2022
Also, please be aware of https://jira.whamcloud.com/browse/LU-15177. A version interop check won’t allow MDT-MDT version skew > 3 minor versions. Note, that check is just about MDT versions.
On 2/21/22, 8:59 PM, "lustre-discuss" <lustre-discuss-bounces at lists.lustre.org> wrote:
The phrasing is a little confusing. The idea is that you can do a rolling upgrade, but it is important to complete the upgrade and not continue running with servers at different versions. Version gaps between servers is OK in the context of a rolling upgrade but not otherwise. That case you are describing - deliberately leaving different versions on different servers - is specifically what you're not supposed to do, because server version interop isn't tested outside the context of a rolling upgrade.
From: lustre-discuss <lustre-discuss-bounces at lists.lustre.org> on behalf of Kurt Strosahl via lustre-discuss <lustre-discuss at lists.lustre.org>
Sent: Monday, February 21, 2022 2:31 PM
To: lustre-discuss at lists.lustre.org <lustre-discuss at lists.lustre.org>
Subject: [lustre-discuss] Upgrading lustre servers
I have a question about upgrading lustre servers...
The lustre manual says the following:
"Lustre software release 2.x.y release (minor) upgrade:
All servers must be upgraded at the same time, while some or all clients may be upgraded.
Rolling upgrades are supported for minor releases allowing individual servers and clients to be upgraded without stopping the Lustre file system."
which seems contradictory. Could I update one oss in a lustre file system from (say) 2.12.1 to 2.12.8, and leave the rest of the file system alone?
Kurt J. Strosahl (he/him)
System Administrator: Lustre, HPC
Scientific Computing Group, Thomas Jefferson National Accelerator Facility
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lustre-discuss