[torquedev] "complete" jobs behavior

Garrick garrick at usc.edu
Mon Feb 1 11:04:46 MST 2010


On Mon, Feb 01, 2010 at 12:03:54PM -0500, Glen Beane alleged:
> On Mon, Feb 1, 2010 at 11:45 AM, Garrick <garrick at usc.edu> wrote:
> 
> > The purpose of "complete" is so the scheduled can read why a job has
> > exited. For that end, the current behavior is correct.
> >
> 
> I can see a running job that gets qdeled end up in the "complete" state so
> the scheduler can see why the job exited, but doesn't it seem strange to
> qdel a job that is in the Q state and have it go to the C state?

It's for the scheduler guys, so it's up to them.

-- 
Garrick Staples, GNU/Linux HPCC SysAdmin
University of Southern California

Life is Good!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torquedev/attachments/20100201/18c051a0/attachment.bin 


More information about the torquedev mailing list