[GE users] array job has taken over

reuti reuti at staff.uni-marburg.de
Wed Aug 12 21:08:32 BST 2009

Am 12.08.2009 um 21:30 schrieb ron:

> You need to setup some scheduler policies, see "Scheduler Policies  
> for Job Prioritization in the N1 Grid Engine 6 System":

Will this also work for array jobs? AFAIK, once an array job was  
scheduled, all tasks are allowed to start.

Another option could be to limit the number of allowed slots per user  
in an RQS, or to limit the active instances of an array job by  
setting max_aj_instances in SGE's configuration (where the default is  

-- Reuti

> http://www.sun.com/blueprints/1005/819-4325.html
>  -Ron
> --- On Thu, 8/13/09, mbay2002 <jeff at haferman.com> wrote:
>> Hi -
>> I'm pretty new to SGE, I know very basic administrative
>> stuff and am
>> still learning.
>> We have a vanilla install with 144 nodes, each with 8
>> cores.  We have
>> not done any policy configuration.
>> A user has submitted an array job with 36000
>> elements.  It was the
>> earliest job submitted, and now her job has taken over
>> every core on the
>> cluster.
>> We have several users waiting who just need a few cores,
>> some just need
>> a single core.  Many of their jobs have a higher
>> priority than the
>> running array job.
>> But, what happens is that everytime the array job index
>> increases,
>> another one starts to execute as the core is freed up.
>> I need some general help in configuring a policy so that
>> her array job
>> is somehow put on hold automatically so that our other
>> users can
>> execute.
>> Jeff
>> ------------------------------------------------------
>> http://gridengine.sunsource.net/ds/viewMessage.do? 
>> dsForumId=38&dsMessageId=212035
>> To unsubscribe from this discussion, e-mail: [users- 
>> unsubscribe at gridengine.sunsource.net].
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do? 
> dsForumId=38&dsMessageId=212044
> 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