QOS (Quality of Service) limits override all other limits.
Association limits override partition limits.
Partition limits (from the slurm.conf file) are also available.
I'll add a hierarchy section to the resource limits web page
Quoting Bill Wichser <[email protected]>:
I'd like to know the ordering of limits applied to a user. Is this
documented anywhere?
Currently I only have limits assigned to a QOS and every job gets
placed into one of these QOS groups. What I'd like to do is to have
an ACCOUNT override this value, or at least have a single user under
an ACCOUNT be able to violate the QOS limits. But perhaps I've
implemented this completely wrong for what I'm hoping to accomplish.
Thanks,
Bill
