[torquedev] "complete" jobs behavior

Garrick garrick at usc.edu
Mon Feb 1 09:45:36 MST 2010


The purpose of "complete" is so the scheduled can read why a job has  
exited. For that end, the current behavior is correct.

HPCC/Linux Systems Admin

On Feb 1, 2010, at 6:53 AM, Ken Nielson  
<knielson at adaptivecomputing.com> wrote:

> Glen Beane wrote:
>> I have to say I am _not_ a fan of qdel'ed jobs going into the
>> "Complete" state.  (maybe starting in 2.4.x?)
>> It makes no sense to me.  How can a job that didn't run and finish on
>> its own be considered "complete".?
>> --- 
>> ---------------------------------------------------------------------
>>
>> _______________________________________________
>> torquedev mailing list
>> torquedev at supercluster.org
>> http://www.supercluster.org/mailman/listinfo/torquedev
>>
> So should we add a 'D' state to confirm it has been deleted and then
> remove the job from the queue when the keep_completed interval  
> expires?
>
> Ken
> _______________________________________________
> torquedev mailing list
> torquedev at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torquedev


More information about the torquedev mailing list