[slurm-users] What is the hide option of scontrol for?

2019-10-24 Thread Uemoto, Tomoki
Hi, all "man scontrol" says: Do not display information about hidden partitions, their jobs and job steps. By default, neither partitions that are configured as hidden nor those partitions unavailable to user's group will be displayed (i.e. this is the default behavior). 'hide' option is

Re: [slurm-users] OverMemoryKill Not Working?

2019-10-24 Thread mercan
Hi; You should set SelectType=select/cons_res and plus one of these: SelectTypeParameters=CR_Memory SelectTypeParameters=CR_Core_Memory SelectTypeParameters=CR_CPU_Memory SelectTypeParameters=CR_Socket_Memory to open Memory allocation tracking according to documentation:

Re: [slurm-users] jobacct_gather/linux vs jobacct_gather/cgroup

2019-10-24 Thread Brian Andrus
IIRC, the big difference is if you want to use cgroups on the nodes. You must use the cgroup plugin. Brian Andrus On 10/24/2019 3:54 PM, Christopher Benjamin Coffey wrote: Hi Juergen, From what I see so far, there is nothing missing from the jobacct_gather/linux plugin vs the cgroup

Re: [slurm-users] jobacct_gather/linux vs jobacct_gather/cgroup

2019-10-24 Thread Christopher Benjamin Coffey
Hi Juergen, From what I see so far, there is nothing missing from the jobacct_gather/linux plugin vs the cgroup version. In fact, the extern step now has data where as it is empty when using the cgroup version. Anyone know the differences? Best, Chris -- Christopher Coffey

[slurm-users] OverMemoryKill Not Working?

2019-10-24 Thread Mike Mosley
Hello, We are testing Slurm19.05 on Linux RHEL7.5+ with the intent to migrate from it toTorque/Moab in the near future. One of the things our users are used to is that when their jobs exceed the amount of memory they requested, the job is terminated by the scheduler. We realize the Slurm