[slurm-users] CR_Core_Memory behavior
Sebastian T Smith
stsmith at unr.edu
Tue Aug 25 21:46:02 UTC 2020
I agree that this may be a node configuration issue. It might also be caused by your resource request. Can you provide your node configuration and an example submission script?
[University of Nevada, Reno]<http://www.unr.edu/>
High-Performance Computing Engineer
Office of Information Technology
1664 North Virginia Street
email: stsmith at unr.edu<mailto:stsmith at unr.edu>
From: slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf of Nizar Abed <nizar at huji.ac.il>
Sent: Tuesday, August 25, 2020 2:38 PM
To: Slurm User Community List <slurm-users at lists.schedmd.com>
Subject: Re: [slurm-users] CR_Core_Memory behavior
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:
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...
More information about the slurm-users