[GE users] SGE-6.0u3: High Priority Queue

Rayson Ho raysonho at eseenet.com
Tue Mar 22 20:26:52 GMT 2005


    [ The following text is in the "iso-8859-1" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some special characters may be displayed incorrectly. ]

>it seems Jobs suspension happens on Hosts/Queue level & not slots
>level. is this correct behavior ????

It is a feature which will be fixed :)

Take a look at:
http://gridengine.sunsource.net/issues/show_bug.cgi?id=35
http://gridengine.sunsource.net/issues/show_bug.cgi?id=1245

And something related:
http://gridengine.sunsource.net/issues/show_bug.cgi?id=548
http://gridengine.sunsource.net/issues/show_bug.cgi?id=1273

IMO, SGE6.0 already scales quite well, and it is time to improve the
scheduler for the next release - esp. we now have so many people migrating
from LSF.

Rayson



>Is this a "feaature" or a "bug" that a single job submitted in
>priority.q suspends all the job slots on any host.???
>
>we have created 2 queues "priority.q" & default "all.q"
>all.q is subordinate of priority.q, on hosts with 4 CPU & 2 CPU job
>slots on hosts.
>when  the hosts are full i.e. 4 jobs & if any priority.q queue job
>lands it suspends all 4 jobs on that host instead of just suspending 1
>job slot.
>Can  any one please confirm this, & what could be possible work arround.
>
>Thanks
>Regards
>
---------------------------------------------------------
Get your FREE E-mail account at http://www.eseenet.com !

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list