Hi Vikrant,
the easiest way to achieve this is to define a custom ressource:
On the machine:
MACHINE_RESOURCE_NAMES = OnePerHost
MACHINE_RESOURCE_OnePerHost = 1
So the submits would need to have:
Request_OnePerHost = 1
The need in the submit file could also be forced by a transform on the AP of course without the user knowing anything about it.
Another way would probably be to run a startd cron counting the actual slot owners of running slots and put those in a list that run more than 2 jobs. The START _expression_ could then grep on that list and not start the job if the user is in the list. I use something sinilar for shutting down nodes for specific groups. If you are interested in taht code snippet let me know :)
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: "Vikrant Aggarwal" <ervikrant06@xxxxxxxxx>
An: "HTCondor-Users Mail List" <htcondor-users@xxxxxxxxxxx>
Gesendet: Dienstag, 16. Juli 2024 22:57:31
Betreff: [HTCondor-users] Limit the number of user jobs a node
Hello Experts,
I have a requirement to limit the number of user jobs on worker nodes. Let's say we have 10 worker nodes with dynamic slots, I want to ensure that user1 can run max 2 jobs on each node not more than that.
I saw the consumption policies to specify custom attributes but we are not using consumption policies, Is it possible to have something like this for dynamic slots when using scheduler level splitting to limit the user to 2 cores per node?
Thanks & Regards,
Vikrant Aggarwal
_______________________________________________
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/