Re: [HTCondor-users] Specify a pool to schedule tasks

[Seung-Jin Sul <ssul@xxxxxxx>]

Thank you!

On Tue, Mar 12, 2024, 8:13âAM Jaime Frey via HTCondor-users <htcondor-users@xxxxxxxxxxx> wrote:

That is correct.

Â- Jaime

On Mar 7, 2024, at 3:52âPM, Seung-Jin Sul <ssul@xxxxxxx> wrote:

Quick question.

So currently I have

```

...
START = True
SUSPEND = False
PREEMPT = False
KILL = False

...

```

in the HTCondor configuration file for the gldeins to the large-mem nodes.

If I set it like

```

...
START = TARGET.RequestMemory > 500000
SUSPEND = False
PREEMPT = False
KILL = False

...

```

, HTCondor masters on the high-mem nodes will be started and ask the schedule to send only ` TARGET.RequestMemory > 500000` tasks to the high-mem nodes? Am I right?

Thanks!

Seung

On Thu, Mar 7, 2024 at 8:39âAM Seung-Jin Sul <ssul@xxxxxxx> wrote:

Hi Jaime,

Thank you for the help. I would like to set the scheduler to send tasks that request small mem only to small-mem nodes not high-mem nodes.Â

Thus, the execution side enforcement will be working for me. Thanks a lot.

Seung

On Thu, Mar 7, 2024, 8:31âAM Jaime Frey via HTCondor-users <htcondor-users@xxxxxxxxxxx> wrote:

This works as a job-side sorting of keeping small jobs on the smaller-memory nodes. Two things to note here:

1) The âMâ suffix to the memory quantity works for the request_memory command in the submit file, but doesnât work in the requirements _expression_. The units for RequestMemory in the job ad and Memory in the slot ad are megabytes. condor_submit translates the âM suffix in request_memory from the submit file when constructing the job ad.

2) You donât need to set requirements for the large-memory jobs at all. Then condor_submit will add the default constraint ofÂ(TARGET.Memory >= RequestMemory).

You can also do execute-side enforcement if you want this policy to apply to all jobs. Youâd modify the START _expression_ of the gldeins on large-memory nodes to be this (along with any other constraints you want):

START = TARGET.RequestMemory > 500000

Â- Jaime

On Mar 5, 2024, at 4:20âPM, Seung-Jin Sul <ssul@xxxxxxx> wrote:

Hi,

We are using a SLURM-based glide-in system. Some of the nodes are high-mem nodes which have 1.5TB memory space and the others have 500GB mem. What could be the best way to schedule tasks to the different pools based `RequestMemory`?





For exmaples:

if `RequestMemory` <= 500GB

===> requirements = (TARGET.Memory >= RequestMemory) && (TARGET.Memory <= 500000M)




else if `RequestMemory` > 500GB and `RequestMemory` <= 1.5TB

===> requirements = (TARGET.Memory >= RequestMemory) && (TARGET.Memory > 500000M) && (TARGET.Memory > 1500000M)







Thank you for your help!




Best,


Seung


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

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

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