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

Re: [Condor-users] Antwort: Re: about different dagman jobs problem

On Fri, 2 Oct 2009, Tao.3.Chen@xxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:

   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

The thing to keep in mind is that DAGMan only controls the order in which jobs go into the queue. Once they're in the queue, the order in which they get run is out of DAGMan's control -- it depends on the matchmaker and various other things.

   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?

You can set priorities either in the DAG files themselves, or in the submit files. If I'm understanding correctly what you want to do, you should set them in the node C submit files. If the C jobs have a higher priority than the A and B jobs, they will essentially jump to the front of the job queue as soon as they're submitted. You don't want to set the priorities for the A and B jobs, because if all of the jobs have a priority of 10, it's the same as not setting priorities at all.

Kent Wenger
Condor Team