Hi!
I just discovered a possible way for a user to abuse the priority in Slurm. This is the scenario:1. A user has not run any jobs in a long time and has therefore has a high fairshare priority. Lets say: 10000.
2. The user submits 1000 jobs into the queue that is far above his fairshare target.
3. The user changes the priority of his job (It's ok for a user to lower the priority of jobs as long as the user is the owner) to lets say: 9999 (still a high priority. +-1 is in practice nothing). (scontrol update jobid=1 priority=9999
4. The users jobs starts and the fairshare priority lowers. But here is the big _BUT_ the jobs with changed priority does not seams to change leaving the users job with maximum priority until all of the jobs are completed.
Have I missed something in this scenario?If this is true what do we do about it? Should users be able to change the priority at all?
The user can use the 'nice' option to alter the priority of a job within a small limit that does not alter the priority as defined above.
Please let me be wrong :-) /Magnus -- Magnus Jonsson, Developer, HPC2N, Umeå Universitet
smime.p7s
Description: S/MIME Cryptographic Signature
