I have found that when a queued job is modified to a different QoS, such as one with a very high priority, or an account that is directly off root with very high shares or any other factor that one would expect to cause the priority to change, it does not immediately do so.
Below is a simple patch that corrects this. Phil Eckert LLNL diff --git a/src/slurmctld/job_mgr.c b/src/slurmctld/job_mgr.c index 396af9b..ff970fe 100644 --- a/src/slurmctld/job_mgr.c +++ b/src/slurmctld/job_mgr.c @@ -7898,6 +7898,12 @@ fini: job_ptr); } } + + /* if successful, Update job priority, since many factors of an update may + * affect priority considerations. */ + if (error_code == SLURM_SUCCESS) + _set_job_prio(job_ptr); + return error_code; }