Scheduler running out of memory when launching a larger (100+) number of nodes simultaneously about cyclecloud-slurm HOT 2 OPEN

We are definitely working on improving that prolog script in the next release. But i just wanted to clarify that it runs on every job launch and not node launch. Also if you are not reliant on the azslurm cost feature or you dont use it then we suggest just commenting out the PrologSlurmctld line in /etc/slurm/slurm.conf. That will just not run the script.

from cyclecloud-slurm.

Thanks for confirming! Looking forward to the next release.

But i just wanted to clarify that it runs on every job launch and not node launch.

That makes sense, I'm running 1-node jobs, so the distinction wasn't clear to me.

from cyclecloud-slurm.