Differences

This shows you the differences between two versions of the page.

--- computing:department:unix:jobs:condor [2010/05/03 15:24] – allan
+++ computing:department:unix:jobs:condor [2015/12/14 16:43] (current) – [Where do jobs run] allan
@@ Line 1: / Line 1: @@
 ====== Condor: Batch/Grid Computing ======
-Batch-style processing is available on select nodes of the Unix cluster via [[http://www.cs.wisc.edu/condor/|Condor]].
+Batch-style processing is available on select nodes of the Unix cluster via Condor.
+Condor is a software framework for distributed parallel computation. At Minnesota, we use it both to manage workload on dedicated server clusters, and (in some cases) to farm out work to idle desktop computers
+Each Physics linux system is tagged with a "CondorGroup" name corresponding to the research group or entity to which it belongs. It is possible to run jobs on any cluster, but if you are unsure whether you should be using a particular group of machines please [[mailto:net@physics.umn.edu?subject=Condor Question|check first]].
+<note>
+You can see which servers belong to each cluster, and what their capabilities are, on the [[https://www.physics.umn.edu/resources/myphys/computing/systems.html|Linux Servers Listing]] page in MyPhys.
-===== Generic Condor Information =====
+If your research group has no computational resources of its own, there is a general-purpose ''phys'' cluster which can be used by anyone.
+</note>
+You can also get an idea of activity within each cluster (although not directly condor-related) at our [[http://monitor.physics.umn.edu/ganglia/|Ganglia monitoring page]]
+===== Lightning Condor Summary =====
 Useful commands for submitting jobs are
@@ Line 18: / Line 26: @@
     * ''condor_q -global'' shows jobs in the global job queue
-For a complete introduction to Condor, please read the Condor Manual:
+You can find some more information at:
+    * [[http://www.cs.wisc.edu/condor/manual/|Condor Manual]]
+    * [[https://condor-wiki.cs.wisc.edu/index.cgi/wiki|Condor Wiki at UW Madison]]
+    * [[http://research.cs.wisc.edu/condor/tutorials/fermi-2005/|Quick Condor Tutorial for Fermilab]]
+===== Submitting batch jobs =====
+==== Use vanilla environment ====
+Unless you've specifically used ''condor_compile'' to build your programs, you'll need to submit your jobs in the "vanilla" universe.
+  universe = vanilla
+==== Limit email output ====
+  Notification = error
-    * [[http://www.cs.wisc.edu/condor/manual/]]
+==== Request slot resources ====
+Almost all our condor slots are set up as "partitionable", which means you can request what resources are needed. Try to specify appropriate values in your submit file so that condor can reserve resources for your job (without this, your job will be given default values which may cause it to be held). For example:
+  request_cpus = 1
+  request_memory = 2048
+==== think about your data access ====
-===== Site Specific Information =====
+Never use your home directory for job i/o - you should probably be using a ''/data'' volume.
+===== Where do jobs run =====
-Nodes are tagged with a ''CondorGroup'' job ClassAd, which allows you to submit jobs to different groups of machines based on where you submit them from. The default behavior means that when you submit a condor job from a physlin workstation or spartha, the job will run on x86 Linux nodes. It is possible to override this behavior in your submit file by manipulating the CondorGroup job ClassAd. For example, you could place the following line in your job file to make the jobs run on the BES3 machines:
+By default, the cluster which executes a job is determined by the machine where you issue the ''condor_submit'' command - for example, if you submit a job from a CMS system, it will execute on the CMS cluster.
-  CondorGroup = "twins"
+You can override this behavior in your submit file by manipulating the CondorGroup job ClassAd. For example, you could place the following line in your job file to make the jobs run on the CMS server farm:
-You should read the manual page for ''condor_submit'' for more details on what can be put in the job file (note though that ''CondorGroup'' is a locally-invented ClassAd, and you won't find any further documentation for it).
+  +CondorGroup = "cmsfarm"
-Some example CondorGroups:
+In addition, you can let your jobs run on **any** cluster, with the condition that it will be pre-empted (ie killed) if a job with a higher rank (based on the group owning the cluster) needs to run. You can enable this behavior with:
+  +CanEvict = True
-  * physlin - Physlin machines (general-purpose linux workstations)
+===== Why won't my job run =====
-  * tpilin  - FTPI linux workstations (FTPI use only!)
-  * twins - BES3 compute farm (BES3 use only!)
-  * minos - MINOS workstations (MINOS use only!)
-  * cms   - CMS servers (CMS use only!)
-  * astro   - Astronomy workstations (Astronomy use only!)
-It is possible to run jobs on any CondorGroup, but if you are unsure whether you should be using a group of machines please [[mailto:net@physics.umn.edu?subject=Condor Question|ask]] first! Anyone may submit jobs to physlin machines, so submitting jobs from a physlin machine (or spartha) are safe bets.
+Some commands to help analyze why your jobs isn't matching
-We currently support the vanilla, standard, and MPI universes.
+  condor_q -analyze <jobid>
+  condor_q -better <jobid>
+Why is job not running on a particular machine
+  condor_q -better <jobid> -machine <name>
+  condor_q -better:reverse -machine <name>

User Tools

Differences

Page Tools