[slurm-users] How to turn off core specialization?
taras.shapovalov at brightcomputing.com
Wed Aug 28 15:20:49 UTC 2019
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.
On Fri, Aug 9, 2019 at 11:54 PM Guertin, David S. <guertin at middlebury.edu>
> 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.
> *David Guertin*
> *Information Technology Services*
> *Middlebury College*
> *700 Exchange St.*
> *Middlebury, VT 05753*
> *From:* slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf of
> Guertin, David S. <guertin at middlebury.edu>
> *Sent:* Friday, August 9, 2019 4:28 PM
> *To:* Slurm User Community List <slurm-users at lists.schedmd.com>
> *Subject:* Re: [slurm-users] How to turn off core specialization?
> > Have you restarted all your slurm daemons?
> Yes, I have done that on every node, but it still shows one specialized
> > Not sure whether "scontrol reconfigure" can deal with that change.
> I tried "scontrol reconfigure", but it also had no effect.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the slurm-users