Indeed, thank you! From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of John M Knoeller <johnkn@xxxxxxxxxxx> condor_submit -i uses a default interative submit file, and when you put ârequest_memory=10000â on the command line that is *prefixed* to the default interactive submit file, so any statement in that submit file that sets memory will override the command line. If you want your request memory statement on the command line to win over the default interactive submit file, just put -append before it. -tj From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of Rundall, Jacob D When I use "request_memory" at the command line it seems to be ignored: $ condor_submit -v -i "request_memory = 10000" | grep "RequestMemory" RequestMemory = 512 Requirements = (TARGET.Arch == "X86_64") && (TARGET.OpSys == "LINUX") && (TARGET.Disk >= RequestDisk) && (TARGET.Memory >= RequestMemory) && ((TARGET.FileSystemDomain == MY.FileSystemDomain) || (TARGET.HasFileTransfer)) ... If I construct a minimal job description file like this and use it for submission then request_memory is honored: $ cat job.int.mem request_memory = 10000 queue 1 $ condor_submit -v -i job.int.mem | grep RequestMemory RequestMemory = 10000 Requirements = (TARGET.Arch == "X86_64") && (TARGET.OpSys == "LINUX") && (TARGET.Disk >= RequestDisk) && (TARGET.Memory >= RequestMemory) && ((TARGET.FileSystemDomain == MY.FileSystemDomain) || (TARGET.HasFileTransfer)) ... I do not have this problem with "request_cpus". E.g., the following works: $ condor_submit -v -i "request_cpus = 4" | grep RequestCpus RequestCpus = 4 Requirements = (TARGET.Arch == "X86_64") && (TARGET.OpSys == "LINUX") && (TARGET.Disk >= RequestDisk) && (TARGET.Memory >= RequestMemory) && (TARGET.Cpus >= RequestCpus) && ((TARGET.FileSystemDomain == MY.FileSystemDomain)
|| (TARGET.HasFileTransfer)) ... This is with HTCondor version 8.8.7. I'd like to be able to request a non-default amount of memory while requesting an interactive job at the command line, without having to use a job description file. Am
I missing something with my syntax, or does anyone have other advice on how to troubleshoot or achieve that goal? |