[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Hooks in the Scheduler Universe?
- Date: Wed, 6 Oct 2010 14:33:02 -0400
- From: Ian Chesal <ichesal@xxxxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Hooks in the Scheduler Universe?
On Wed, Oct 6, 2010 at 10:28 AM, David Arthur <mumrah@xxxxxxxxx>
I'm hoping to use the Job Hook system for DAGs. I would like to
utilize the "prepare job" and "job exit" hooks (to get notifications
when the DAG is about to start, and once it's complete).
I don't want to knock too much on hooks, but unless you're using them on non-Windows nodes I wouldn't recommend this approach. The technology is still unstable on Windows. It's very easy to crash a startd.
I've never considered running *just* the prepare_job hook, without a corresponding fetch_work hook.
The technology is condor_starter specific I believe. The scheduler universe doesn't use a condor_starter to run its jobs as far as I'm aware.
I would use the SCRIPT PRE/POST functionality, but it seems to only be
on a Node basis rather than the whole graph. The topology of jobs I'm
submitting does not have a "first" or "last" node.
I'll second what Todd send about nested DAGs. I think you're better off going this route and nesting in a simple DAG that does your pre and post executes.