Re: [HTCondor-users] Why doesn't HTCondor-CE support the standard RequestMemory attribute?

[Jaime Frey <jfrey@xxxxxxxxxxx>]

Years ago, we had reports from multiple CE admins of incoming jobs that had a RequestMemory value that was the default supplied by condor_submit. That value was too small and so the jobs would fail. There wasnât a good way in the CE to detect if the value was the default supplied by condor_submit, so we deicded to always ignore it. The factories for glideins always use the attribute maxMemory, which the CE copies to RequestMemory, so they werenât affected by the change.

Thinking about it now, itâd be better to apply a minimum value for the incoming RequestMemory instead of ignoring it. Iâm going to look into making that change.

 - Jaime

> On Sep 25, 2025, at 6:50âAM, KÃhn, Max (SCC) <max.fischer@xxxxxxx> wrote:
> 
> Hi all,
> 
> Weâve lately had multiple user groups confused by HTCondor-CE handling the standard RequestCPU and RequestMemory attributes. Specifically, RequestCPU is purposely used but RequestMemory is purposely ignored in the transforms.
> I am considering to patch our CEs to handle both attributes consistently to avoid hard to spot usage errors. Of course, that raises the questionâ
> 
> Why *does* HTCondor-CE discard RequestMemory? Is there some pitfall or negative effect of using this attribute that I might not be considering?
> 
> Cheers,
> Max
> 
> [0]
> https://github.com/htcondor/htcondor-ce/blob/2b86fd9977ffc19385b8fcaffc012d3895c7664d/config/01-ce-router-defaults.conf#L175-L179
> 
> [1]
> https://github.com/htcondor/htcondor-ce/blob/2b86fd9977ffc19385b8fcaffc012d3895c7664d/config/01-ce-router-defaults.conf#L232C55-L236
> 
> _______________________________________________
> 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/