If we use job-wide limit enforcement, the exclusive jobs are also killed once the requested resources are exceeded even though the node is fully dedicated to the job. We should have a mom’s config variable to configure this behavior.
For example: Let’s have a node with 32 cpus and a job with request for 16 cpus exclusively. If the job is started on the node, no other jobs can run on the same node and thus some limitations can be ignored. It can be useful to allow the job to use the node without job-wide limitations like ncpus or mem. Of course the limits for walltime or cputime are still applied.
Please provide your feedback.