2014-11-12 17:06 GMT+01:00 David Lipowitz <[email protected]>:
> Hi, > > We're doing a SLURM proof-of-concept and the management of temp space is > really important for what we want to do. We set up a few virtual machines > as a test with the following slurm.conf settings: > > FastSchedule=2 > SelectType=select/cons_res > SelectTypeParameters=CR_CPU_Memory > NodeName=test[1-3] NodeAddr=xxx.xxx.xxx.[1-3] CPUs=4 State=UNKNOWN > TmpDisk=1024 RealMemory=512 > > > The CPUs setting above works as expected: We see jobs waiting when number > of jobs per node exceeds 4, so that's good. > > We also see jobs waiting when the total memory consumption as specified > using sbatch's --mem option exceeds the RealMemory setting. Also good. > > But we can't get jobs to wait when TmpDisk is exceeded using the sbatch's > --tmp option. Any suggestions? > As far as I remember --tmp is not treated as consumable resource, you can define license (if the the filesystem is shared) or gres if it's per computing node, and setup quota in prologue/epilogue using this values. cheers, marcin
