<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>We generally upgrade within 1-2 maintenance windows of a new
release coming out, so within a couple of months of the release
being available. For minor updates, we update at the next
maintenance window. At one point, we were stuck several release
behind. Getting all caught up wasn't that bad. I think were were
on 15.something and upgrading to 17.11, or something like that.</p>
<p>For that upgrade, most of the work happened on the DB server, I
upgraded one-at-a-time through each release until we were current
on the SlurmDB, and then made a single upgrade to the latest
version on the slurm controller and compute nodes. <br>
</p>
<p>Our Slurm DB is small, so the upgrade changes to the DB only took
a few minutes per upgrade. For larger DBs, it can take hours per
upgrade.</p>
<p> This is one reason people like to keep current with Slurm - it
makes future upgrades that much easier. On maintenance window of
only a couple hours is more palatable than a couple of days of
downtime. Also, when you jump several updates, it's hard to tell
when a new "feature" or "bug" was introduced, which makes
identifying the source and fixing/understanding the new behavior
that much harder. <br>
</p>
<p>Prentice<br>
</p>
<div class="moz-cite-prefix">On 12/18/20 1:10 PM, Jason Simms wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAP7JYwcA=9JmUiq_NaFk8iWN1G_y93Y2vZ=fzPq5cserYx7_eA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hello all,
<div><br>
</div>
<div>Thanks to several helpful members on this list, I think I
have a much better handle on how to upgrade Slurm. Now my
question is, do most of you upgrade with each major release?</div>
<div><br>
</div>
<div>I recognize that, normally, if something is working well,
then don't upgrade it! In our case, we're running 20.02, and
it seems to be working well for us. The notes for 20.11 don't
indicate any "must have" features for our use cases, but I'm
still new to Slurm, so maybe there is a hidden benefit I can't
immediately see.</div>
<div><br>
</div>
<div>Given that, I would normally not consider upgrading. But as
I understand it, you cannot upgrade more than two major
releases back, so if I skip this one, I'd have to upgrade to
(presumably) 21.08, or else I'd have to "double upgrade" if,
e.g., I wanted to go from 20.02 to 22.05.</div>
<div><br>
</div>
<div>To prevent that, do most people try to stay within the most
recent two versions? Or do you go as long as you possibly can
with your existing version, upgrading only if you absolutely
must?</div>
<div><br>
</div>
<div>Warmest regards,</div>
<div>Jason<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;margin:0px"><span
style="color:rgb(130,36,51)"><font
face="Century Gothic"><b>Jason L. Simms,
Ph.D., M.P.H.</b></font></span></div>
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;margin:0px"><font
face="Century Gothic"><span>Manager of
Research and High-Performance Computing</span></font></div>
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;margin:0px"><font
face="Century Gothic"><span>XSEDE Campus
Champion<br>
</span><span style="color:gray">Lafayette
College<br>
Information Technology Services<br>
710 Sullivan Rd | Easton, PA 18042<br>
Office: 112 Skillman Library<br>
p: (610) 330-5632</span></font></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>