l partitions at the same priority, and using
QOS instead for priority/preemption -- that has the unfortunate side effect of
tying down your QOS's to be used for that purpose, but it works for our
situation.
Best of luck,
-Matt
Matt Jay
Sr. HPC Systems Engineer - Hyak
Research Computing
Univ
Corey,
Are the partitions over the same nodes by chance? If so, you could be hitting
this:
https://bugs.schedmd.com/show_bug.cgi?id=3881
"This is by design. If there are _any_ jobs pending (regardless of the reason
for the job still pending) in a partition with a higher Priority, no jobs from
g PI partition has
higher priority).
We had to adapt the model we were planning to use many smaller higher priority
'condo' partitions (in terms of node count) instead of fewer large ones --
still not ideal, but in practice it works okay for us.
Matt Jay
Sr. HPC Systems Engineer - Hya
sn't impact resource request/requirements for
an individual job).
The best approach will depend on the particulars of the job itself, but setting
"--ntasks-per-core" in conjunction with the "--ntasks=30" would be one way to
allow a job with more tasks than the core cou
mber of cores available in the partition).
Matt Jay
HPC Systems Engineer - Hyak
Research Computing
University of Washington Information Technology
From: slurm-users [mailto:slurm-users-boun...@lists.schedmd.com] On Behalf Of
Matt Hohmeister
Sent: Thursday, September 26, 2019 9:14 AM
To: slurm-us...@sch
