[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Submitting MPI JOb
- Date: Sun, 22 Jun 2008 23:22:26 -0500
- From: Matthew Farrellee <mfarrellee@xxxxxxxxxx>
- Subject: Re: [Condor-users] Submitting MPI JOb
I have a question about MPI job.
When I submitted MPI job, the change between Idle state to Running State
took long time (about 5 to 10 minutes). Condor seems need some time to get
the dedicated resource being claimed.
But other condition happen, when I issued command condor_hold and
condor_release, a few second after that, job state can change quickly.
Does anyone know why this happen ?
The negotiation cycle for Condor happens periodically, default is every
It's possible that it took more than one negotiation cycle for the
Schedd to get enough claims to start your job.
If your question is why did your job start up quickly the second time,
it is possible the Schedd still had those claims to start your job up
quickly after the hold+release.
If your question is why does your job go on Hold or become Idle after
being release quickly, it's because the Schedd can make those changes
directly without having to rely on other parts of the system.