[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] condor submit and dag man

I doubt it.

First off, I assume you mean the schedd when you say condor_submit.

- Job dependencies are DAGMan's bread and butter, so for as long as
there's a DAGMan it seems like there's no reason to duplicate that
code in the schedd.

- MaxRunning might make sense to have on a per-user breakdown in the
schedd, or at least have a more fine-grained control that the
schedd-wide MAX_JOBS_RUNNING config setting. If the job ad could refer
to the queue then you could do this today, ie something like:
   requirements = TARGET.OpSys == "LINUX" &&
(count(localqueue.runningjobs) < 50)
(to be clear, I just made that syntax up, so don't try it and expect it to work)

-MaxIdle doesn't seem very useful for the schedd

As far as emulating them with other tools, that's what DAGMan is for.
What are you trying to do that doesn't work for you?


On Fri, Apr 9, 2010 at 2:20 PM, Mag Gam <magawake@xxxxxxxxx> wrote:
> Will Condor's DAGMan features ever be migrated to condor_submit? For
> example, having job dependencies and MaxRun and MaxIdle options...
> If not, is it possible to emulate these features with other tools?
> _______________________________________________
> 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/