[gridengine users] will changes to a hard limit in a queue config roll down into running jobs?

Reuti reuti at staff.uni-marburg.de
Thu Nov 15 16:45:53 UTC 2012


Am 15.11.2012 um 17:31 schrieb Jesse Becker:

> On Thu, Nov 15, 2012 at 11:20:33AM -0500, Chris Dagdigian wrote:
>> 
>> Quick question ...
>> 
>> I've got a job with a user running in a queue that has a 48 hour hard
>> wallclock limit. The user is prepared to move into a long.q but his job
>> is *almost* complete and will not go much past the 48h limit. Trying to
>> see if I can preserve the job and not lose 48 hours of computation...
> 
> I'm pretty sure changing the jobs on the queue will not propagate down
> to the jobs.  The limits are set using ulimit

CPU time yes (h_cpu/s_cpu is an SGE *and* ulimit), but the wallclock time is observed only by SGE (man queue_conf).

-- Reuti


> by the shepherd, which is
> then inherited by the actual job processes.
> 
> You might be able to use some "external" program to tweak the values.  A
> quick check of the Googles mentions this:
> 	http://karelzak.blogspot.co.uk/2012/01/prlimit1.html
> 
> 
>> 
>> If I relax or remove the hard limit from the cluster queue config
>> temporarily will the job be spared? Do changes to these limits get
>> passed down dynamically to running jobs.  I can't remember if I've ever
>> had this particular scenario come up before...
>> 
>> Regards,
>> Chris
>> 
>> 
>> _______________________________________________
>> users mailing list
>> users at gridengine.org
>> https://gridengine.org/mailman/listinfo/users
> 
> -- 
> Jesse Becker
> NHGRI Linux support (Digicon Contractor)
> _______________________________________________
> users mailing list
> users at gridengine.org
> https://gridengine.org/mailman/listinfo/users




More information about the users mailing list