[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] No history traces of flocked jobs on my condor master?
- Date: Tue, 6 Sep 2011 17:54:34 -0700 (PDT)
- From: Rob <spamrefuse@xxxxxxxxx>
- Subject: Re: [Condor-users] No history traces of flocked jobs on my condor master?
On Fri, 02 Sep 2011 08:58:58 Matthew Farrellee wrote:
>> On 09/01/2011 06:27 PM, Rob wrote:
>> I'd like to know information of the jobs which have been flocked to my condor master.
>> However, it seems to me that these jobs do not leave any traces.
>> Is that so?
>> I try
>> condor_history -l | grep<some typical string of the flocking machine>
>> and this renders nothing....
>> Any ideas?
> There is no central location and condor_* tool for this, but there are mechanisms you can use. For instance, the Negotiator writes a MatchLog, which would have information about flocked jobs. Also Startds can be configured to write a history file (STARTD_HISTORY, read by condor_history) or each job that runs can be left in a STARTD_PER_JOB_HISTORY_DIR. You'll have to collect yourself though.
Hmmm, I'm surprised it is so difficult to get this information about flocked-in jobs.
Is it intentionally so that flocked-in jobs are not stored in the history files of a condor master? Or is it "not yet implemented"?
In order to keep track of the master's full history and possibly keep track of who did what on the condor pool, it would be better if the condor master would keep ALL its processed jobs in its history data base, including the ones that were flocked-in from another condor system.....