Condor is a specialized workload management system for compute-intensive jobs. Like other full-featured batch systems, Condor provides a job queueing mechanism, scheduling policy, priority scheme, resource monitoring, and resource management.
Users submit their serial or parallel jobs to Condor, Condor places them into a queue, chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion.
While providing functionality similar to that of a more traditional batch queueing system, Condor's novel architecture allows it to succeed in areas where traditional scheduling systems fail. Condor can be used to manage a cluster of dedicated compute nodes (such as a "Beowulf" cluster).
In addition, unique mechanisms enable Condor to effectively harness wasted CPU power from otherwise idle desktop workstations. For instance, Condor can be configured to only use desktop machines where the keyboard and mouse are idle.
Should Condor detect that a machine is no longer available (such as a key press detected), in many circumstances Condor is able to transparently produce a checkpoint and migrate a job to a different machine which would otherwise be idle.
Condor does not require a shared file system across machines - if no shared file system is available, Condor can transfer the job's data files on behalf of the user, or Condor may be able to transparently redirect all the job's I/O requests back to the submit machine. As a result, Condor can be used to seamlessly combine all of an organization's computational power into one resource.
Condor monitors a pool of machines to find idle machines that are then used to complete submitted jobs, and also provides remote system and checkpointing mechanisms that allow for transparent remote execution and job migration.
NOTE: To be able to download product you will have to provide an e-mail address and your name on the developer's website.
What's New in This Release: [ read full changelog ]
· Machine slots can now be configured to identify and divide customized local resources. Jobs may then request these resources. See section 3.12.8 for details. (Ticket #2905).
· Condor now supports and implements the caching of ClassAds to reduce memory footprints. This feature is experimental and is currently disabled by default. It can be enabled by setting the new configuration variable ENABLE_CLASSAD_CACHING to True. (Ticket #2541). (Ticket #3127).
· condor_status now returns the condor_schedd ClassAd directly from the condor_schedd daemon, if both options -direct and -schedd are given on the command line. (Ticket #2492).
· The new -status and -echo command line options to condor_wait command cause it to show job start and terminate information, and to print events to stdout. (Ticket #2926).
· Added a DEBUG logging level output flag D_CATEGORY, which causes Condor to include the logging level flags in effect for each line of logged output. (Ticket #2712).
· condor_status and co...