I think someone asked this same exact question a few weeks ago. The best
solution I know of is to use Arbiter, which was created exactly for this
situation. It uses cgroups to limit resource usage, but it adjusts those
limits based on login node utilization and each users behavior ("bad"
users get their resources limited more severely when they do "bad" things.
I will be deploying it myself very soon.
https://dylngg.github.io/resources/arbiterTechPaper.pdf
<https://dylngg.github.io/resources/arbiterTechPaper.pdf>
Prentice
On 4/23/21 10:37 PM, Cristóbal Navarro wrote:
Hi Community,
I have a set of users still not so familiar with slurm, and yesterday
they bypassed srun/sbatch and just ran their CPU program directly on
the head/login node thinking it would still run on the compute node. I
am aware that I will need to teach them some basic usage, but in the
meanwhile, how have you solved this type of user-behavior problem? Is
there a preffered way to restrict the master/login resources, or
actions, to the regular users ?
many thanks in advance
--
Cristóbal A. Navarro
