[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Condor Call back mechanism
- Date: Thu, 31 May 2007 14:47:49 +0000
- From: Hemant Tanwar <hemant_tanwar@xxxxxxxxxxx>
- Subject: Re: [Condor-users] Condor Call back mechanism
We do not want to manually tail the log file. Because the jobs are submitted by the system on demand and there is no human being involved. so we need to build a system ( via software programs) , which will automatically take certain action after job is finished by condor.
Manipulating with the log file is not that sophisticated.
Registering a perl module has a shortcoming.... if we submit 4000 jobs there will be 4000 perl module running and listening on status of job which may kill the system.
So we wanted to handles inside condor and when it finishes a job, we want to put a message in Message Queue or put a record in a database.
The Condor 7.0 release will have logs in database, and we can put DB triggers to achieve the same thing. But I do not know how to achieve this in current release of condor.
> Date: Thu, 31 May 2007 07:20:57 -0500
> From: epaulson@xxxxxxxxxxxx
> To: condor-users@xxxxxxxxxxx
> Subject: Re: [Condor-users] Condor Call back mechanism
> On 5/31/07, Kewley, J (John) <j.kewley@xxxxxxxx> wrote:
> > One of the config values is the location of the mail program. I have
> > considered using my
> > own program there instead and parsing the "mail message" sent to it, but
> > have never tried it.
> > I'd be interested in finding out if that was possible.
> I don't see why it wouldn't work, though obviously the mail messages
> aren't the most parse-friendly pieces of data.
> Another option is to use DAGMan with a POST script for each job to
> submit your jobs. You can have a very wide DAG with no parent-child
> relationships, and your jobs basically run just as before.
> Another option is to tail the job logfile yourself, and when you see a
> terminate event you can do whatever you want. (Tailing the logfile is
> how DAGMan works) If you use the Condor Perl module, you can register
> a perl subroutine as a callback and it will take care of the tailing
> for you, and you can register different callbacks on different sorts
> of exits (one callback for exit with success, a callback for exit with
> failure, a callback for evicted, etc). The only bummer about the perl
> module is you have to let the perl module do the submitting (again,
> like DAGMan.)
> > JK
> > -----Original Message-----
> > From: condor-users-bounces@xxxxxxxxxxx
> > [mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of
> > Hemant Tanwar
> > Sent: Thursday, May 31, 2007 6:10 AM
> > To: condor-users@xxxxxxxxxxx
> > Subject: [Condor-users] Condor Call back mechanism
> > Hi,
> > I have a question on Condor Call back mechanism.
> > When it finishes a job, it can send email that the job is done. But is it
> > possible to take some other action like "executing a shell script" or
> > putting a message in MQ.
> > Basically we like to do some thing other than just getting email when the
> > job is complete by Condor.
> > Is there any way to achieve this ?
> > Thanks,
> > Hemant
> > ________________________________
> > Palate Teasers: Straight from Master Chef! Sanjeev Kapoor
> > _______________________________________________
> > Condor-users mailing list
> > To unsubscribe, send a message to
> > condor-users-request@xxxxxxxxxxx with a
> > subject: Unsubscribe
> > You can also unsubscribe by visiting
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> > The archives can be found at:
> > https://lists.cs.wisc.edu/archive/condor-users/
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at:
Sign in and get updated with all the action! Formula One