I'm not sure I understand why your app must decide the placement, rather
then tell Slurm about the requirements (This sounds suspiciously like
Not Invented Here syndrome), but Slurm does have the '-w' flag to
salloc,sbatch and srun.
I just don't understand if you don't have an entire cluster
There's an enum job_states in slurm.h. It becomes OUT_OF_MEMORY, &c. in the
job_state_string function in slurm_protocol_defs.c.
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
Not sure if this is correct but I think you need to leave a bit of RAM for the
OS to use so best not to allow slurm to allocate ALL of it. I usually take 8G
off to allow for that - negligible when our nodes have at least 768GB of RAM.
At least this is my experience when using cgroups.
Emyr Jame
Dear all,
I am working on a script to take completed job accounting data from the slurm
accounting database and insert the equivalent data into a clickhouse table for
fast reporting
I can see that all the information is included in the cluster_job_table and
cluster_job_step_table which seem to