Next: 10.3 Upgrading from the
Up: 10. Version History and
Previous: 10.1 Introduction to HTCondor
10.2 Development Release Series 8.5
This is the development release series of HTCondor.
The details of each version are described below.
- HTCondor version 8.5.5 released on June 6, 2016.
- The EC2 GAHP now rate-limits its requests, and responds to overload
warnings with an exponential back-off. Additionally, fewer operations are
now performed on a per-job basis (as few as one in some cases). The
resulting scalability improvements have been demonstrated to permit a single
GAHP to manage ten thousand instances. Because the overload condition is
account- and region- specific, the grid manager now launches a GAHP for
each account-region pair. We therefore recommend adding D_PID to
EC2_GAHP_DEBUG, for disambiguation, and this is now the default.
- The grid manager now assigns HoldReasonCodes and
HoldReasonSubCodes to EC2 jobs when they go on hold. Values are
subject to change until the stable release.
- The grid manager now advertises some metrics from the EC2 GAHP.
- Some Linux distributions for supercomputer compute nodes and
others distributions for docker images have no /var/run/utmp. HTCondor no longer
aborts when this file is missing, when it tries to determine keyboard
idle times, it just assumes these kinds of machines have no keyboards.
- Docker Universe jobs now correctly advertise RemoteUserCpu
and RemoteSysCpu in their job ad and in the job log file.
- A batch name specified for a DAG (with the condor_submit_dag
-batch-name option) is now propagated to all jobs of that DAG,
- The batch name for a condor_dagman job (if not set) now
defaults to DagFile+cluster (where DagFile
is the primary DAG file of the condor_dagman job, and cluster
is the HTCondor cluster of the condor_dagman job).
Because the batch name is now propagated throughout a workflow, if
no batch name is specified, the batch name for all jobs in the
workflow will be DagFile+cluster of the top-level
- The files named in the submit file attributes vm_disk,
xen_kernel, and xen_initrd now refer to
locations on the execute machine.
condor_submit no longer modifies these values or checks for their
existence on the submit machine.
If these files need to be transferred by HTCondor, then they should be
listed in transfer_input_files and their presence in
these vm universe attributes shouldn't include any path information.
- In the python bindings, an ExprTree can be cast to an integer
or floating point value.
- HTCondor now supports the following systemd features: Socket Activation,
Watchdog, Status message, and journald logging. In these release, the
Socket Activation is not configured, because the security system is not
prepared to properly handle the socket passed in from outside HTCondor.
- Added config knob DEFAULT_MASTER_SHUTDOWN_SCRIPT to
specify a default program to exec as root upon condor_master exit.
See Section 3.3.8 for details.
- Fixed a bug that caused file transfers to fail when using Bosco.
- HTCondor version 8.5.4 released on May 2, 2016.
- The deltacloud type in the grid universe, which allowed
submission to Deltacloud services, has been removed.
- condor_status can now display the utilization of a condor_startd with
a single line of output for each machine rather than a line per slot.
In this release this output is enabled by passing -compact to condor_status
but in a future release this will be the default output of condor_status.
- Improved the performance of the condor_collector by
not computing dropped update statistics, statistics which
have never been accessible by users.
- The performance of the condor_history tool has been
- condor_user_prio now queries the condor_collector for
accounting information by default, when appropriate. This should be
much faster than the older way of querying the condor_negotiator. The
old path is still available by passing the -negotiator option to the
- The default value of DAGMAN_ALWAYS_RUN_POST has been
changed from True to False. This means that, by
default, if the PRE script of a DAG node fails, the POST script
of the node will not be run. (This had been the default
behavior until version 7.7.2. The 7.7.2-8.5.3 behavior can be
restored by setting DAGMAN_ALWAYS_RUN_POST to
True, or by passing the new -AlwaysRunPost
argument to condor_submit_dag.)
- The batch_gahp can now submit multi-core jobs to HTCondor.
- The batch_gahp's ability to generate a limited X.509 proxy
for use by the job on the execute machine can now be disabled, which is now
- The condor_schedd will now send submitter ad updates for idle submitters
less frequently than updates for submitters that have jobs in the queue. There
are two new configuration variables to control this behavior.
ABSENT_SUBMITTER_LIFETIME is the number of seconds after the last
job for that submitter leaves the queue that the submitter will continue to
send updates to the condor_collector. It defaults to 1 week.
ABSENT_SUBMITTER_UPDATE_RATE is the maximum rate in seconds at which
the condor_schedd will send updates to the condor_collector for a submitter
that has no jobs in the queue. It defaults to 5 minutes.
- Fixed a bug that caused the condor_schedd to exit when receiving
an updated X.509 proxy for a job.
- In expressions in the Job Router's configuration, attributes no
longer require a 'TARGET.' scope prefix.
- Fixed a bug in condor_q -xml that would put the XML header
after the body unless -stream was passed.
- HTCondor version 8.5.3 released on March 24, 2016.
- ENABLE_IPV4 and ENABLE_IPV6 both now accept
the special value "AUTO", which is true if an interface with the corresponding
protocol exists on the host, and false otherwise.
- ENABLE_IPV4 and ENABLE_IPV6 both now default
to the special value "AUTO". Additionally, the new configuration macro
PREFER_IPV4 is true by default. This macro causes HTCondor to
prefer IPv4 over IPv6 when choosing an address to advertise, when choosing
the address of daemon looked up in the collector, and when resolving DNS
- New configuration macros added: IPV4_ADDRESS,
- New attributes have been added to the Submitter ClassAd to indicate
the number of Idle and Running jobs for Scheduler universe and for Local
- Jobs can now be submitted to the SLURM batch scheduling system via
the new slurm type in the grid universe.
- In addition to logging to the file KERNEL_TUNING_LOG,
the default LINUX_KERNEL_TUNING_SCRIPT now also logs to
syslog and /etc/systcl.d/99-htcondor.conf.
- condor_history -autoformat now supports the j option to print
job ids like condor_q does.
- HTCondor is now built and linked with Globus 6.0.
- Pre-size the ClassAd hash table to improve the performance of the
condor_collector when getting ClassAd updates.
- The negotiator now forwards accounting information to the collector,
where it can be easily queried and monitored.
- Fixed a bug on condor_history that could result in truncation of
the job id field.
- HTCondor version 8.5.2 released on February 18, 2015.
- On Windows, configuring HTCondor to restrict the range of outbound
port numbers may cause substantial delays when using the command-line
tools. Since we now know that it's not free to do so, LOWPORT
and HIGHPORT no longer restrict the port numbers of outbound
connections on Windows. If you still require this functionality, use
OUT_LOWPORT and OUT_HIGHPORT.
- Fixed a bug that could cause a daemon to be in the wrong
privilege state when attempting to act as the user.
- The condor_startd history file now contains the peak
memory usage, by an exited job, not the more recent.
- When the condor_starter evicts a job, perhaps because
it has exceeded a memory limit, it does not transfer back to
the submit machine the sandbox of working files. This is
consistent with other types of holds.
- The condor_startd now advertises the following attributes
on Linux machines: CpuFamily CpuModelNumber CacheSize. These are
pulled from the /proc/cpuinfo file.
- condor_q has a new option -schedd-constraint which can be used
to constrain the queues displayed when using the -global option.
- When an HTCondor-C job is submitted to a remote condor_schedd,
the remote job ad now includes the attribute SubmitterGlobalJobId,
whose value is the same as the attribute GlobalJobId in the
original HTCondor-C job.
- The condor_schedd now sets environment variables for scheduler
universe jobs so that the jobs can more easily find the condor_schedd's
On machines where there are multiple condor_schedds running, this helps
DAGMan and similar applications contact the condor_schedd that started
- When SEC_ENABLE_MATCH_PASSWORD_AUTHENTICATION is set
to True, the related authorizations are now automatically enabled.
Previously, submit-side@matchsession and
execute-side@matchsession entries had to be added to the
ALLOW_DAEMON and ALLOW_CLIENT (if set)
authorization parameters in order for this feature to work.
- HTCondor version 8.5.0 released on October 12, 2015.
- The condor_startd history file contains two new attributes: BadputCausedByDraining and BadputCausedByPreemption, two boolean-valued attributes which are true if the job was evicted not by a user request.
- The python bindings have a new Claim API, allowing Computing-On-Demand (COD) to be
invoked via python.
- The python bindings can now submit multiple distinct processes using the submitMany
method, similar to a condor_submit file with multiple queue statements.
- The python bindings now provide improved support for managing multiple concurrent queries.
- As an experimental feature, the python bindings implement the HTCondor negotiation protocol.
- Changed "Condor" to "HTCondor" in condor_dagman
output (mainly in the dagman.out file).
- The new configuration parameter JOB_SPOOL_PERMISSIONS
controls the permissions on a job's spool directory managed by the
condor_schedd on unix.
It defaults to the value user, which results in a permissions
value of 0700.
Other valid values are group (permissions 0750) and
world (permissions 0755).
Previously, all job spool directories had access permissions of 0755.
- The condor_schedd no longer changes the ownership of spooled job
files that it manages.
Now, the files are always owned by the submitting user.
The previous behavior of changing ownership to/from the condor
account can be restored by setting the new configuration parameter
CHOWN_JOB_SPOOL_FILES to True.
Next: 10.3 Upgrading from the
Up: 10. Version History and
Previous: 10.1 Introduction to HTCondor