[GE users] 6.2u3 and exclusive host access, is urgency policy required?

andy andy.schwierskott at sun.com
Wed Jul 29 21:55:09 BST 2009


there's no need to define an urgency > 0.

Well, the urgency for an exclusive attribute does, what it does for any
other complex attribute: raise or not raise the pending job priority. How
much is defined by the relative weight_urgency value vs. other urgencies.


On Wed, 29 Jul 2009, craffi wrote:

> Hi folks,
> Via documentation here:
> http://wikis.sun.com/display/gridengine62u3/Configuring+Exclusive+Scheduling
> ... shows a sensible complex entry for a new attribute that allows
> exclusive host access without the "threaded PE" hack or
> otherworkarounds that we are used to.
> New complex looks like this:
> #name shortcut type relop requestable consumable default urgency
> exclusive excl BOOL EXCL YES YES 0 1000
> My question is, why are there 1000 urgency tokens associated with the
> complex entry? Is that really required for exclusive host scheduling
> to work or can I just set it to zero?
> -Chris
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=210140
> To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].


To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].

More information about the gridengine-users mailing list