On Mon, Oct 12, 2026 at 01:58:12PM +0200, Steffen Grunewald via slurm-users wrote:
I have now received a request to provide individual CPU cores as well, so "shared mode" would be it.
I cannot quite get what you mean by this. Are you trying to utilize more than one job on the CPU cores?
Our compute nodes are 2s/16c/2t, "slurmd -C" on them reports CPUs=64 Boards=1 SocketsPerBoard=2 CoresPerSocket=16 ThreadsPerCore=2
Moving those jobs (that claim "never to be runnable") to the new partition now appears to work, and they claim enough memory not to share their node with other jobs, but I'd like to keep them in their original partition.
If you set up `OverSubscribe=EXCLUSIVE` on the default partition, and your job is requesting CPUs=32, slurm will allocate CPUs=64 (max. accroding to your configuration) regardless, because of exclusiveness.
Where's my mistake? Am I trying to mix things that can't be mixed?
I cannot say for sure untill there is a glimpse of your slurm.conf :/ Maybe there are enough job on the exclusive partitions already? With the similar setup I know, slurm config goes something like ``` PartitionName=Default OverSubscribe=NO PartitionName=Priority_special OverSubscribe=EXCLUSIVE ``` -- Monish.