Re: [HTCondor-users] BOSCO question

[Zhuo Zhang <zhuo.zhang@xxxxxxxx>]

Hi Greg,

Thanks for the reply. But unfortunately flocking is not what I am 
looking for. Jobs from pool A flock to pool B will have to go through 
machine A first, which is still a single point of failure.

Thanks,

Zhuo


On 8/31/2017 3:52 PM, Greg Thain wrote:
> On 08/29/2017 10:44 AM, Zhuo Zhang wrote:
> > Hi Greg,
> >
> > Thanks for the reply. The reason that I am asking the job submission 
> > manager is that we have three small HTCondor pools, we want something 
> > that can submit jobs to multiple clusters simultaneously in order to 
> > fully utilize the resources. 
>
> HTCondor can do this itself, and there are several different ways to 
> do so.
>
> If you want this to happen for all jobs submitted to any of the three 
> pools, perhaps the easiest way is with flocking.
>
> When a condor_schedd flocks to a remote pool, any idle jobs that don't 
> match in the local pool are sent to one or more remote pools. For each 
> schedd that you want to flock to a remote pool, just set in that 
> schedd's config file:
>
> FLOCK_TO = remotePool1
>
> and in the central manager of remotePool1 one, add the name of the 
> schedd machine in the FLOCK_FROM line
>
> FLOCK_FROM = remoteSchedd
>
> There are several other ways to join pools together, but for a small 
> number of pools under the same administrative control, I'd start with 
> flocking.
>
> -greg
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx 
> with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/

--
Zhuo Zhang, ASSISTT
I.M. Systems Group (IMSG), NOAA/NESDIS/STAR
5825 University Research Court, Suite 1500 (IMSG), Cube 1500-11
College Park, MD 20740
Tel: (240) 582-3585 (x23017)