[slurm-users] CR_Core_Memory behavior

Durai Arasan arasan.durai at gmail.com
Tue Aug 25 16:49:48 UTC 2020


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?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20200825/8367fa17/attachment.htm>

More information about the slurm-users mailing list