Subject: [Condor-users] Antwort: Re: about different dagman jobs problem
Hi,Kent, Thank you so much for your reply, I
realized something, so the job order in different dags is based on the
submit time of each job, right? Actually in every dag I have 3 jobs, A,B,C, Parent
A B CHILD C, so I want after A,B finished, C can be executed as soon as
possible, but the real situation is I submitted several dags in one executor
machine,there are already many jobs queueing in this executor, so job C
has to wait until the jobs in front of it finish, then C can run. Is this
the way DAGMan works? To solve this problem, how about I just
set job C "priority=10", so that C can have the highest access
to run? The issue is I can not set job A,B to priority=10, could this be
a problem?
Thanks again!
Tao
"R. Kent Wenger"
<wenger@xxxxxxxxxxx> Gesendet von: condor-users-bounces@xxxxxxxxxxx
10/01/2009 04:52 PM
Bitte antworten an
Condor-Users Mail List <condor-users@xxxxxxxxxxx>
An
Condor-Users Mail List <condor-users@xxxxxxxxxxx>
Kopie
Thema
Re: [Condor-users] about different dagman
jobs problem
On Thu, 1 Oct 2009, Tao.3.Chen@xxxxxxxxxxxxxxxxxxxxxxxxxxx
wrote:
> I am using DAGMan to submit specific order jobs, I submit
2 different
> dagman jobs to same executor PC(I have only one executor) :
>
> dag1:
> JOB testA testA.sub
> JOB testB testB.sub
> JOB testC testC.sub
> PARENT testA testB CHILD testC
>
> dag2:
> JOB testD testD.sub
> JOB testE testE.sub
> JOB testF testF.sub
> PARENT testD testE CHILD testF
>
> But the result is: the executor will always execute
> testA,testB,testD,testE,and then testC,testF, it is not what I want.
I
> need condor first finish dag1,then dag2,not like first all parent
jobs
> testA,testB,testD,testE, then child jobs testC,testF, does anyone
have
> this kind of problem? How can I solve this problem?
> Thank you in advance!
Remember that there is no order of jobs guaranteed between separate DAGs.
Basically, you have two choices: make everything into one big DAG, or
create a "parent" DAG that runs the two sub-DAGs.
If you make everything into once big DAG, you would do the following in
a single DAG file:
JOB testD testD.sub
JOB testE testE.sub
JOB testF testF.sub
PARENT testA testB CHILD testC
PARENT testC CHILD testD testE
PARENT testD testE CHILD testF
If you want a parent DAG, you'd do the following:
dag_parent:
SUBDAG EXTERNAL first dag1
SUBDAG EXTERNAL second dag2
PARENT first CHILD second
(You would need to keep your existing dag1 and dag2, and only submit
dag_parent.)
You can also use the SPLICE keyword, which works similarly to SUBDAG
EXTERNAL in terms of dependencies, but runs everything under a single
DAGMan instance:
dag_parent
SPLICE first dag1
SPLICE second dag2
PARENT first CHILD second
(Note that the above discussion assumes that you're running a pretty
recent Condor -- 7.3.x or late 7.2.x. If you have an older Condor
version, you'll have to do things a bit differently.)
For more information, see sections 2.10.6.7 and 2.10.6.8 of the Condor
manual:
http://www.cs.wisc.edu/condor/manual/v7.3/2_10DAGMan_Applications.html#SECTION003106700000000000000
http://www.cs.wisc.edu/condor/manual/v7.3/2_10DAGMan_Applications.html#SECTION003106800000000000000
Kent Wenger
Condor Team
_______________________________________________
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/
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}