Hi, 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?
- Sebastian -- [University of Nevada, Reno]<http://www.unr.edu/> Sebastian Smith High-Performance Computing Engineer Office of Information Technology 1664 North Virginia Street MS 0291 work-phone: 775-682-5050<tel:7756825050> email: stsm...@unr.edu<mailto:stsm...@unr.edu> website: http://rc.unr.edu<http://rc.unr.edu/> ________________________________ From: slurm-users <slurm-users-boun...@lists.schedmd.com> on behalf of Nizar Abed <ni...@huji.ac.il> Sent: Tuesday, August 25, 2020 2:38 PM To: Slurm User Community List <slurm-users@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, Nizar On Aug 25, 2020, at 19:51, Durai Arasan <arasan.du...@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
