Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Confused: condor_q -name option with flocking
- Date: Fri, 19 Aug 2005 11:10:00 +0100
- From: John Horne <john.horne@xxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Confused: condor_q -name option with flocking
On Thu, 2005-08-18 at 09:34 -0500, Jaime Frey wrote:
> On Aug 18, 2005, at 6:49 AM, John Horne wrote:
>
> >
> > The confusion is what do I actually specify for the '-name' option?
> > What is 'a schedd name'? For the '-pool' option I have been specifying
> > the FQDN of the server I am flocking to, I have done the same with the '-name'
> > option and that seems to work (I can see the job queue on the remote
> > server). But what then is the point of having to use both '-pool' and
> > '-name' if they are both the same?
>
> The short answer is that you don't care about condor_q -name when
> flocking. Yours jobs are in your local schedd's queue and no other
> queue.
>
> Now the long answer: A Condor pool is defined by the central manager
> (the collector, really). All Condor daemons that report to the same
> collector are part of the same pool. A pool only has one central
> manager (there are options for hot spares, but let's ignore them). A
> pool can have many schedds, each with its own queue of jobs.
>
[snipped]
Many thanks for the reply. It is a good explanation! :-)
John.
--
---------------------------------------------------------------
John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914
E-mail: John.Horne@xxxxxxxxxxxxxx Fax: +44 (0)1752 233839