Hi,

I have some questions about partition priority values defined in slurm.conf file. I use:

PriorityType=priority/multifactor
PriorityDecayHalfLife=0
PriorityUsageResetPeriod=NONE
PriorityFavorSmall=YES
PriorityMaxAge=14-0
PriorityWeightAge=1000
PriorityWeightFairshare=0
PriorityWeightJobSize=1000
PriorityWeightPartition=10000
PriorityWeightQOS=100000
PreemptType=preempt/partition_prio
PreemptMode=SUSPEND,GANG


I have same nodes on two partition with different partition priority values, all other values are the same for these two partions..
let say :
PartitionName=lowprio Nodes=node[1-10] Default=no State=UP Shared=NO Priority=1000 PartitionName=hiprio Nodes=node[1-10] Default=no State=UP Shared=NO Priority=2000

I am sending the same jobs to every partitions,
PRIORITY JOBID       ACCOUNT  PARTIT  CPUS  NODELIST(REASON
13976    4052106  user         hiprio   16   1 (Resources)
12976    4052108  user         lowpri   16   1 (Resources)

and then increase the job priorities of jobs in lower-priority partition with "scontrol update jobid= .." to a value more than the ones in higher priority partition.

PRIORITY JOBID       ACCOUNT  PARTIT  CPUS  NODELIST(REASON
13976    4052106  user         hiprio   16   1 (Resources)
16000    4052108  user         lowpri   16   1 (Resources)


After I make the nodes idle, normally I expect the the jobs has higher priority should be run before the lower-priority jobs, but in realty jobs which has lower priority values ( jobs at higger priority partition) starts more early..
PRIORITY JOBID       ACCOUNT  PARTIT  CPUS  NODELIST(REASON
13976    4052106  user         hiprio   16   1 node1
16000    4052108  user         lowpri   16   1 (Resources)

I was thinking that partition priorities are used only to determine the job priority. Do I miss something or made some wrongs? I have searched hr list archive, there were similar questions for slurm-2.6 but there was no relevant answer.. we use slurm-13.12.0


Regards...

Sefa Arslan

Reply via email to