<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">In the “other ramifications” category, if you aren’t already planning to, you might consider making this change during a maintenance period when all jobs are drained. We tried to change from SelectType=select/linear to SelectType=select/cons_res
on the fly once (via “scontrol reconfig”) and discovered that slurm can not preserve the job states with this change – all running jobs were lost. I don’t know if changing SelectTypeParameters would have the same result or not. But be safe, I would stop
all jobs and back up your StateSaveLocation before making that change. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">slurm-users <slurm-users-bounces@lists.schedmd.com> on behalf of Liam Forbes <loforbes@alaska.edu><br>
<b>Reply-To: </b>Slurm User Community List <slurm-users@lists.schedmd.com><br>
<b>Date: </b>Thursday, May 10, 2018 at 7:29 PM<br>
<b>To: </b>"slurm-users@lists.schedmd.com" <slurm-users@lists.schedmd.com><br>
<b>Subject: </b>[slurm-users] impact of changing SelectTypeParameters?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Might there be any "adverse" impacts to changing SelectTypeParameters=CR_CPU to SelectTypeParameters=CR_Socket_Memory? Our compute nodes are, for the most part, exclusive so users are allocated entire nodes, no sharing, for jobs. We explicitly
specify CPUs, Sockets, CoresPerSocket, & ThreadsPerCore for all our compute nodes.<br>
<br>
I assume --nodes, --ntasks, & --cpus-per-task would all work the same, for example, wouldn't they?
<br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Would something change in the accounting that would make reporting on numbers of cpu hours or size of jobs change?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Other ramifications?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">Regards,<br>
-liam<br>
<br>
-There are uncountably more irrational fears than rational ones. -P. Dolan<br>
Liam Forbes <a href="mailto:loforbes@alaska.edu" target="_blank">loforbes@alaska.edu</a> ph: 907-450-8618 fax: 907-450-8601<br>
UAF Research Computing Systems Senior HPC Engineer CISSP<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>