Re: [HTCondor-users] Negotiator only allocating 1 job per machine per cycle

["Valdes, Julio" <Julio.Valdes@xxxxxxxxxxxxxx>]

Hello Todd:

Thank you very much for your feedback.
I shall try what you suggested and see if I could get the desired behavior.
Regards,

Julio J. ValdÃs
National Research Council Canada                                    | Conseil National de Recherches Canada 
Digital Technologies Research Centre                               | Centre de Recherche en Technologies NumÃriques
Data Science for Complex Systems Group                        | Science des DonnÃes pour les SystÃmes Complexes
M-50, 1200 Montreal Road, Ottawa, Ontario K1A 0R6 | M-50, 1200 chemin MontrÃal, Ottawa, Ontario K1A 0R6 
Canada                                                                                     | Canada 
julio.valdes@xxxxxxxxxxxxxx
tel/tÃl: (1)613-993-0257


-----Original Message-----
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Todd L Miller
Sent: Thursday, September 02, 2021 5:36 PM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Negotiator only allocating 1 job per machine per cycle

***ATTENTION*** This email originated from outside of the NRC. ***ATTENTION*** Ce courriel provient de l'extÃrieur du CNRC

> I assume that such definition should be done by adding directives 
> within the condor_config file of the given worker. Could you please 
> provide an example that I could use as a starting point?

        The canonical way to dedicate an entire machine's resources to a single partitionable slot is as follows (entries go in the worker machine's HTCondor configuration):

        # from https://htcondor.readthedocs.io/en/latest/admin-manual/policy-configuration.html#index-136

        NUM_SLOTS = 1
        NUM_SLOTS_TYPE_1 = 1
        SLOT_TYPE_1 = 100%
        SLOT_TYPE_1_PARTITIONABLE = TRUE

HTCondor has mechanisms to reserve CPUs, memory, and disk for the use of the system; look RESERVED_DISK and RESERVED_MEMORY up in the manual (CPUs are a little more complicated, IIRC).


        As Christoph said, when you submit jobs with request_cpu, request_memory, and request_disk, HTCondor will not start jobs which request more resources than are available.  There are various mechanisms for enforcing the requested limits, if that becomes necessary.  You can also configure HTCondor to reject jobs that don't specify those three request values, or to set default values.

- ToddM
_______________________________________________
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/