[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] job submission using condor-G to gt4



On Dec 17, 2005, at 3:40 AM, Vinodh wrote:

      u r right. the problem was with the
filesystemdomain. it is different in all the nodes.

      i am having one more doubt. now i added one more
line in the job description file "requirements = Arch
== Linux".

then, i submitted this file using condor_submit.
condor_g submits this job fine.
the condor_q -ana is

204.000:  Run analysis summary.  Of 13 machines,
     13 are rejected by your job's requirements
      0 reject your job because of their own
requirements
      0 match but are serving users with a better
priority in the pool
      0 match but reject the job for unknown reasons
      0 match but will not currently preempt their
existing job
      0 are available to run your job

WARNING:  Be advised:
   No resources matched request's constraints
   Check the Requirements expression below:

Requirements = (Arch == Linux)

Requirements and 'condor_q -ana' have no affect on Condor-G jobs if you're not explicitly using match-making. If you were submitting a vanilla universe job, you'd have to use this as your requirements: Arch=="LINUX"
Note the double quotes and LINUX in all caps.

the globus job is submitted as vanilla universe job in
another machine.
condor_q -ana on that machine is

011.000:  Run analysis summary.  Of 13 machines,
     13 are rejected by your job's requirements
      0 reject your job because of their own
requirements
      0 match but are serving users with a better
priority in the pool
      0 match but reject the job for unknown reasons
      0 match but will not currently preempt their
existing job
      0 are available to run your job
        No successful match recorded.
        Last failed match: Sat Dec 17 15:07:14 2005
        Reason for last match failure: no match found

WARNING:  Be advised:
   No resources matched request's constraints
   Check the Requirements expression below:

Requirements = (OpSys == "LINUX" && Arch == "INTEL")
&& (Disk >= DiskUsage) && ((Memory * 1024) >=
ImageSize) && (TARGET.FileSystemDomain ==
MY.FileSystemDomain)

my question is "how to change these requirements, from
where the condor picks these values?"

Condor adds sensible defaults for the requirements expression (run on a machine with the same architecture and shared filesystem and enough memory). If you mention these attributes explicitly in your requirements expression, then Condor won't add them.

In this case, Globus is the one writing the submit file. Look in $GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/condor.pm. One warning: Globus assumes your pool has a shared filesystem, so if you don't have a shared filesystem, then just disabling the FileSystemDomain check won't be enough for jobs to run correctly.

+----------------------------------+---------------------------------+
|            Jaime Frey            |  Public Split on Whether        |
|        jfrey@xxxxxxxxxxx         |  Bush Is a Divider              |
|  http://www.cs.wisc.edu/~jfrey/  |         -- CNN Scrolling Banner |
+----------------------------------+---------------------------------+