On 7/19/22 00:45, gphipps wrote:
Hi
Everyone so often one of our users accidentally writes a “fork-bomb” that
submits thousands of sbatch and srun requests per second. It is a giant
DDOS attack on our scheduler. Is there a way of rate limiting these
requests before they reach the daemon? I could imagine writing a shim in
front of sbatch/srun, but I was hoping there was an official way to do this
Perhaps setting MaxSubmitJobs and MaxJobs on associations and QOSes would
do the trick?
You may also want to increase the default MaxJobCount in slurm.conf.
See my Wiki page for the details:
https://wiki.fysik.dtu.dk/niflheim/Slurm_configuration#maxjobcount-limit
/Ole
