Generally the way we've solved this is to set aside a specific set of
nodes in a partition for interactive sessions. We deliberately scale
the size of the resources so that users will always run immediately and
we also set a QoS on the partition to make it so that no one user can
dominate the partition.
-Paul Edmon-
On 6/11/2020 8:49 AM, Loris Bennett wrote:
Hi Manual,
"Holtgrewe, Manuel" <manuel.holtgr...@bihealth.de> writes:
Hi,
is there a way to make interactive logins where users will use almost no resources
"always succeed"?
In most of these interactive sessions, users will have mostly idle shells running and do
some batch job submissions. Is there a way to allocate "infinite virtual cpus"
on each node that can only be allocated to
interactive jobs?
I have never done this but setting "OverSubscribe" in the appropriate
place might be what you are looking for.
https://slurm.schedmd.com/cons_res_share.html
Personally, however, I would be a bit wary of doing this. What if
someone does start a multithreaded process on purpose or by accident?
Wouldn't just using cgroups on your login node achieve what you want?
Cheers,
Loris
