Hi Herbert,
I believe the limit is per node (not per partition) whereas you want it per
job. In other words, your users will be able to run jobs on other nodes.
There is no MaxCPUsPerJob option in the partition definition, but I believe
you can make that restriction in other ways (at worst with a
Look into the documentation on a QOS on the sacctmgr page. A QOS can be
defined via sacctmgr, and that QOS can be attached to the partition to allow
for more restrictions than just the partition definition allows.
One of the settings for a QOS is "MAXTRESPerJob", so setting that to "cpu=8",
an
We have a cluster with multi-core nodes (168) that can be shared by
multiple jobs at the same time. How do I configure a partition such that
it only accepts jobs requesting up to (say) 8 cores, but will run
multiple jobs at the same time? The following is apparently not working:
PartitionName=
Thank you Markus, I fixed the error and figured out how that happened so it
shouldn't happen that way again!
Thanks again,
--Tim
--
Tim McMullan
Release Management, Support, and Development
SchedMD LLC - Commercial Slurm Development and Support
On Wed, Feb 26, 2025 at 4:13 AM Markus Köberl via s
Hi,
there was this issue raised some time ago:
https://www.mail-archive.com/slurm-users@lists.schedmd.com/msg10799.html
We're experiencing exactly the same issue now with GPU nodes in power saving,
some (but not all) jobs doesn't start because of that, and it's annoying users
- badly.
Anyone
On Tuesday, 25 February 2025 22:10:02 CET Marshall Garey via slurm-users
wrote:
> We are pleased to announce the availability of Slurm versions 24.11.2
> and 24.05.6.
On the download page the wrong md5sum is displayed for slurm-24.11.2.tar.bz2
regards
Markus Köberl
--
Markus Koeberl
Graz Unive
