[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Dagging deeper in priorities and ranks
- Date: Wed, 18 Jul 2007 12:22:23 +0100
- From: "Matt Hope" <matthew.hope@xxxxxxxxx>
- Subject: Re: [Condor-users] Dagging deeper in priorities and ranks
On 7/18/07, Horvátth Szabolcs <szabolcs@xxxxxxxxxxxxx> wrote:
After investigating the usage of the DAGManJobId attribute as job
priority I found some strange results.
These are the JobPrio attribute results of the used expressions:
priority = $(DAGManJobId) = DAGManJobId
priority = -1 * $(DAGManJobId) = -1
priority = 50000000 - $(DAGManJobId) = 5000000
priority = (50000000 - $(DAGManJobId)) = 0
It looks as if only the first attribute (or number) of the expression is
used and the rest is skipped.
With this limitation its impossible to do what is described in the docs
because it forces the exact opposite!
"This allows, for example, a user to automatically set the relative
local queue priority of jobs based on the condor_dagman job that
submitted them, so that jobs submitted by ``older'' DAGs will start
before jobs submitted by ``newer'' DAGs (assuming they are otherwise
Any information on this topic is much appreciated.
(Using 6.9.2 on winXP.)
6.8.1 fixed a bug which prevented this being set correctly - I assumed
that it was also in 6.9 (or at least at 6.9.2) but perhaps it isn't...