Hello David,
thank you, this might be a simple and a viable solution to this problem. I'll
test both
(yours and Megan) solutions and then decide.
Kind regards
--
On Sun, Mar 30, 2025 at 08:19:12AM -0600, Davide DelVento via slurm-users wrote:
Hi Kamil,
I don't use QoS, so I don't have a dire
Hello Megan,
this looks like a solution, thank you!
The reason I asked for an option
that can be set once for only one QoS (that should be preempted by all other
OoSes)
is that I use Ansible for managing my users, and I have a YAML file with all
users data. I was hoping to avoid adding an optio
Hi Kamil,
It is possible to set all QOS's "Preempt" value with two sacctmgr commands. For
example, if all the existing QOS have PreemptMode as "cluster", which seems
likely if this is the first time QOS preemption is being set up, then you can
set the PreemptMode of the targeted QOS to "suspend
Hi Kamil,
I don't use QoS, so I don't have a direct answer to your question, however
I use preemption for a queue/partition and that is extremely easy to set up
and maintain. In case you plan with QoS won't work, you can set up a
preemptable queue and force this user to submit only to this queue a
