Re: [Condor-users] Vanilla jobs not automatically restart

[Preston Smith <psmith@xxxxxxxxxx>]

Hi Dan,

We use JobRunCount while processing history for usage tracking. (In  
some cases we compute a job's "billable" time differently if it  
restarts.)

If we upgrade to 6.9.5 or greater, will our usage processing scripts  
need to be updated to use NumJobStarts instead of JobRunCount?

Does "deprecated" imply "don't use it, it'll go away soon" or  
"JobRunCount won't appear any more effective now"?


-Preston


On Nov 28, 2007, at 2:03 PM, Dan Bradley wrote:

> > Dan,
> > 	I am confused by the distinction between JobRunCount and  
> > NumJobStarts.
> > Would you be willing to enumerate the circumstances when these two  
> > numbers can
> > differ?
>
> JobRunCount is deprecated in 6.9.5.  As it was implemented in previous
> versions, it is basically equivalent to the new NumShadowStarts
> attribute, which is the number of times the schedd has started up a
> submit-side shadow process for the job.  Frequently, the number of
> shadow starts and the number of times the job starts are equal, but  
> they
> can differ.  For example, if the power goes off on the submit node and
> the schedd restarts before the job lease expires (default 20 minutes),
> then the schedd can start up a new shadow to remotely watch over the
> still running job.  In this case, the number of shadow starts will be
> greater than the number of job starts.
>
> --Dan

--
Preston Smith  <psmith@xxxxxxxxxx>
Systems Research Engineer
Rosen Center for Advanced Computing, Purdue University