<div dir="ltr">Hi Dave,<div><br></div>I can confirm that CoreSpecCount can not be reset to 0 once it is set >0 (at least for FastSchedule>0). As a workaround for this bug you can try to stop slurmctld, remove node_state file and start slurmctld again.<div><br></div><div>Best regards,</div><div><br></div><div>Taras</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 9, 2019 at 11:54 PM Guertin, David S. <<a href="mailto:guertin@middlebury.edu">guertin@middlebury.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
What's even stranger is that I can change CoreSpecCount to any other number (2, 3, whatever), restart the daemons, and the change is made. But if I try to set it to 0, nothing happens. It's like there's a setting somewhere that is forcing CoreSpecCount to be
>0. But I have no idea what that could be.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Dave<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div id="gmail-m_-8356403504872941730Signature">
<div name="divtagdefaultwrapper">
<font color="#008080"><i>David Guertin</i></font>
<div><font color="#008080"><i>Information Technology Services</i></font></div>
<div><font color="#008080"><i>Middlebury College</i></font></div>
<div><font color="#008080"><i>700 Exchange St.</i></font></div>
<div><font color="#008080"><i>Middlebury, VT 05753</i></font></div>
<div><font color="#008080"><i>(802)443-3143</i></font></div>
</div>
</div>
<div id="gmail-m_-8356403504872941730appendonsend"></div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_-8356403504872941730divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> slurm-users <<a href="mailto:slurm-users-bounces@lists.schedmd.com" target="_blank">slurm-users-bounces@lists.schedmd.com</a>> on behalf of Guertin, David S. <<a href="mailto:guertin@middlebury.edu" target="_blank">guertin@middlebury.edu</a>><br>
<b>Sent:</b> Friday, August 9, 2019 4:28 PM<br>
<b>To:</b> Slurm User Community List <<a href="mailto:slurm-users@lists.schedmd.com" target="_blank">slurm-users@lists.schedmd.com</a>><br>
<b>Subject:</b> Re: [slurm-users] How to turn off core specialization?</font>
<div> </div>
</div>
<div class="gmail-m_-8356403504872941730BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="gmail-m_-8356403504872941730PlainText">> Have you restarted all your slurm daemons?<br>
<br>
Yes, I have done that on every node, but it still shows one specialized core. <br>
<br>
> Not sure whether "scontrol reconfigure" can deal with that change.<br>
<br>
I tried "scontrol reconfigure", but it also had no effect.<br>
<br>
Thanks,<br>
Dave<br>
<br>
</div>
</span></font></div>
</div>
</blockquote></div>