Hi David, Baker D.J. <[email protected]> writes:
> Hello, > > I guess that may a simple question for someone more experienced with slurm > scheduling than us. When jobs are queuing in our cluster we find that we get > a lot of these messages in our slurmctld.log > > error: Job 25766 priority exceeds 32 bits > > I cannot find any mention or discussion of this type of error in the mailing > list archives, and so I wondered if someone could please explain how to > prevent these errors. We have tried reducing the fair share > component to no avail…. > > PriorityWeightAge=1000 > > PriorityWeightFairshare=10 > > PriorityWeightJobSize=1000 > > PriorityWeightPartition=1000 > > PriorityWeightQOS=1 # don't use the qos factor > > Best regards, > > David You would need to show us a little more information. The weights are just that - weights. If you had, say, a partition with a very large priority, then multiplying it by 1000 could push the total priority over the size of a 32-bit integer. What kinds of values does 'sprio -l' show? Cheers, Loris -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email [email protected]
