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

Re: [HTCondor-users] Concurrency Limits with Flocking

Hi Matt

Just testing at this stage as we have the "possibility" of some licensed
software being used. For software using say, a license manager of some sort, this
would not be a problem. From what I understand this particular licensed software
is more depending on the "goodwill" of the user/s.

We would like to offer them a solution using Condor that we can tell them will
"honour" the number of concurrently running instances.



-----Original Message-----
From: Matthew Farrellee [mailto:matt@xxxxxxxxxx] 
Sent: Thursday, 28 March 2013 9:45 AM
To: HTCondor-Users Mail List
Cc: Hitchen, Greg (CESRE, Kensington)
Subject: Re: [HTCondor-users] Concurrency Limits with Flocking

On 03/08/2013 12:47 AM, Greg.Hitchen@xxxxxxxx wrote:
> Just a quick question for those in the know.
> Does Condor's implementation of concurrency limits work across pools 
> that allow flocking between them?
> My simple understanding from reading the manual would be no. It only 
> works within a pool, as it relies on the collector/negotiator for enforcement?
> If that is the case, then is it possible to setup a global concurrency 
> limit across multiple pools?
> At this stage this is a slightly academic question but may be 
> necessary for us in the future.
> Thanks
> Cheers
> Greg

Concurrency limits are scoped to a pool. The negotiator is responsible for managing the concurrency limits.

Flocking is a schedd opportunistically talking to a negotiator in a foreign pool. A foreign pool where the administrators have explicitly allowed you to flock.

You can construct a global concurrency limit, assuming you can configuration on the flock of negotiators.

What's the use case you're considering?