Re: [Condor-users] Preventing Condor from automatically insertingmemory comparisons

[Dan Bradley <dan@xxxxxxxxxxxx>]

The automatic memory requirements are only suppressed if you explicitly 
use Memory in your requirements expression, not VirtualMemory.  It can 
even be a NOP such as the following:

Memory =!= UNDEFINED

--Dan

Ian Chesal wrote:

> I have the following in my submission ticket:
>
> requirements = ((VirtualMemory >= ImageSize) && (Arch == "INTEL" &&
> (OpSys == "WINNT40" || OpSys == "WINNT50" || OpSys == "WINNT
> 51")))
>
> And for each job that I call queue for I set:
>
> +ImageSize = <my best guess>
> queue
>
> But Condor is insisting on appending a Memory to ImageSize comparison
> for me in the final requirements for the job. When I do condor_q
> -analyze I see:
>
> ((VirtualMemory >= ImageSize) && (Arch == "INTEL" && (OpSys == "WINNT40"
> || OpSys == "WINNT50" || OpSys == "WINNT51"))) && (Disk >= DiskUsage) &&
> ((Memory * 1024) >= ImageSize) && (HasFileTransfer)
>
> The ((Memory *1024) >= ImageSize)) is preventing my job from being
> matched. I was under the impression that the memory portion would only
> be appended automatically if there wasn't anything in the requirements
> already that made a memory comparison. But I have explicitly told it I
> want to use available virtual memory not static, divided memory for each
> vm as the matching factor.
>
> How can I stop the automatic addition of the static memory to image size
> comparison?
>
> - Ian
>
>
> --
> Ian R. Chesal <ichesal@xxxxxxxxxx>
> Senior Software Engineer
>
> Altera Corporation
> Toronto Technology Center
> Tel: (416) 926-8300
>
>
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> http://lists.cs.wisc.edu/mailman/listinfo/condor-users
>