Re: [Condor-users] Condor Job Requirements

[Robert Futrick <rfutrick@xxxxxxxxxxxxxxxxxx>]

Hello Balamrali,

The condor_submit command automatically appends these extra 
requirements, the assumption being that you want the job to run on 
machine similar to the one you're currently submitting from. To change 
this, put a bit more in your requirements expression that would 
accurately describe your jobs' requirements. For example, you could use 
the following expression:

Requirements = (OpSys=="LINUX") && (Arch =="INTEL" || Arch == "X86_64") 
&& (Memory > 1) && (Disk > 1000)

To determine why your jobs are not executing, try running the "condor_q 
-better-analyze" command. That should help diagnose which of the 
individual requirements in the expression is keeping the jobs from 
matching any slots.

I hope this helps. Good luck!

Regards,
Rob

Balamurali Ananthan wrote:
> Hello,
>
> All I have in my job command file is just this requirement:
>
> Requirements = (OpSys=="LINUX")
>
> But after I submit my job, when I see my job class ad using 'condor_q 
> -l' , I see this.
>
> Requirements = ((OpSys == "LINUX")) && (Arch == "INTEL") && ((CkptArch 
> == Arch) || (CkptArch =?= UNDEFINED)) && ((CkptOpSys == OpSys) || 
> (CkptOpSys =?= UNDEFINED)) && (Disk >= DiskUsage) && ((Memory * 1024) >= 
> ImageSize)
>
>  From where does all these extra requirements gets appended to my 
> original job requirement, that always gets my job being rejected because 
> of a "no match found"?
>
> Thanks!
>
>   
--

===================================
Rob Futrick
main: 888.292.5320

Cycle Computing, LLC
Leader in Condor Grid Solutions
Enterprise Condor Support and CycleServer Management Tools

http://www.cyclecomputing.com
http://www.cyclecloud.com