[slurm-users] CR_Core_Memory behavior

Nizar Abed nizar at huji.ac.il
Tue Aug 25 21:38:15 UTC 2020

Sounds like you didn’t define RealMemory for NodeName in slurm.conf(?)

All the best,

> On Aug 25, 2020, at 19:51, Durai Arasan <arasan.durai at gmail.com> wrote:
> Hello,
> On our cluster we have SelectTypeParameters set to "CR_Core_Memory".
> Under these conditions multiple jobs should be able to run on the same node. But they refuse to be allocated on the same node and only one job runs on the node and rest of the jobs are in pending state.
> When we changed SelectTypeParameters to "CR_Core" however, this issue was resolved and multiple jobs were successfully allocated to the same node and ran concurrently on the same node.
> Does anyone know why such behavior is seen? Why does including memory as consumable resource lead to node exclusive behavior?
> Thanks,
> Durai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20200826/eb1e6d83/attachment.htm>

More information about the slurm-users mailing list