Hello everybody,
confusing:
https://slurm.schedmd.com/archive/slurm-18.08.8/news.html
"
RELEASE NOTES FOR SLURM VERSION 19.05
28 May 2019
...
"
Bug-tracking is only via commercial support?
Regards,
Benjamin
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 no
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:
https://slurm.schedm
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 version
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
High-Performance
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 prefers
Hello out there!
I am a pretty fresh slurm user running a cluster of three nodes. For our
other services i have an icinga2.service to monitor our servers. Now i like
to integrate slurm into this environment. The Host check and other
standards are done with the normal plugins, but i want also to kno
