[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Duplicate ClusterIds in condor_history
- Date: Wed, 3 May 2006 16:32:10 -0500
- From: Dan Bradley <dan@xxxxxxxxxxxx>
- Subject: Re: [Condor-users] Duplicate ClusterIds in condor_history
The schedd state is contained in $SPOOL/job_queue.log. Did your schedd
restart around the time that this happened?
On May 3, 2006, at 3:53 PM, Preston Smith wrote:
I was just checking some condor_history output, and noticed I'd
gotten two jobs
returned with the same ClusterId.. Looking further, it seems that
Condor on this
particular submission host decided to jump backwards 5000-some
and is is now merrily reusing them.
Where does Condor decide what the next ClusterId is? I did recently
filesystem strangeness on ~condor about when the jump-back occurred,
wonder if some state file's been corrupted? Any ideas on how to get
it back on
track to minimize the duplicates?
Preston Smith <psmith@xxxxxxxxxx>
Systems Research Engineer
Rosen Center for Advanced Computing, Purdue University
Condor-users mailing list