On 02/23/2010 09:50 PM, Raymond Mancy wrote:
I've got a Q about the Job v RecipeSet priorities.
When we last spoke you mentioned how changing the Priorities of a Job would cause these
changes to be filtered down to the RecipeSets.
I've got a couple of questions about this.
If you are changing(say increasing) the priority of a Job, the priority of this Job would
be increased amongst a pool of other Jobs.This means that this Job will possibly run
sooner than what it would have previously. To then though increase the priority of a
RecipeSet within the Job, which is competing for cpu time within a different pool
(consisting of it and other RecipeSets), doesn't make immediate sense to me. Also if
you change all the RecipeSet priorities to that of the containing Job is kind of a moot
point anyway isn't it? Because once the Job is selected, it has a bunch of RecipeSets
to run, all with the same priority.
Because I'm not really too ofey with the working of the Scheduler, I've probably
just missed something along the way.
The Scheduler doesn't look at the job. If you notice there is no place
to store priority for a job. Having a UI to change a job priority is
just a handy way of changing all the recipesets priority at once. It
keeps the user from having to go through each recipeset to change the
If the only recipeSets queued all have the same priority then yes,
nothing will change. But usually we have more than one jobs recipesets
running or queued at once.