... which can be to your advantage if you split negotiators for different types of machines or batch ressource types e.g. GPUS or interactive batch etc. - very conveniant then ;)
Best
christoph
--
Christoph Beyer
DESY Hamburg
IT-Department
Notkestr. 85
Building 02b, Room 009
22607 Hamburg
phone:+49-(0)40-8998-2317
mail: christoph.beyer@xxxxxxx
Von: "Jaime Frey via HTCondor-users" <htcondor-users@xxxxxxxxxxx>
An: "HTCondor-Users Mail List" <htcondor-users@xxxxxxxxxxx>
CC: "Jaime Frey" <jfrey@xxxxxxxxxxx>
Gesendet: Donnerstag, 9. Januar 2025 18:14:12
Betreff: Re: [HTCondor-users] Concurrency limits and multiple negotiators
Your suspicion is correct. The negotiator enforces concurrency limits across all slots and jobs that it matches.
If you have multiple negotiators, they do not coordinate on enforcing concurrency limits.
- Jaime
On Jan 9, 2025, at 7:16âAM, Jeff Templon <templon@xxxxxxxxx> wrote:
Yo,
Weâre thinking about using concurrency limits to help solve an issue here on the local cluster. Reading the documentation, it seems a perfect match:
This limit is applied globally to all jobs submitted from all schedulers across one HTCondor pool
However, later I read that the resources need to be defined
in the negotiatorâs configuration file
Since we have multiple negotiators here, itâs hard to see how these limits will be in effect globally across the pool. My guess is that this piece of the docs had forgotten that it was assuming Thou Shalt Only Have One Negotiator. I thought it worth
checking here : is that correct? That the limits are not pool-wide, they are ânegotiator segment wideâ which in many cases means pool wide, but not always? Or am I missing something?
JT
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
The archives can be found at: https://www-auth.cs.wisc.edu/lists/htcondor-users/