request_virtualmemory
If I set request_virtualmemory seems to be ignored now (8.9.11). Condor= 2G, condor_submit accepts it as a valid knob but the job stays idle and never runs.
request_memory = 3G
= 1G
request_virtualmemory = 2G
If I set request_virtualmemory =
...
2000000, which should be the same as 2G, the job runs but doesn't set memory.memsw.limit_in_bytes in the cgroup.
Nodescheduler
We found a way to implement our nodescheduler script in Slurm using the --exclude option. Is there a way to exclude certain hosts from a job? Or perhaps a constraint that prevents a job from running on a node that is already running a job of that user? Is there a better way than this?
...