This is the development release series of HTCondor.
The details of each version are described below.
Version 8.3.1
Release Notes:
HTCondor version 8.3.1 released on September 11, 2014.
New Features:
If cgroups are enabled on Linux platforms,
the amount of swap space used by a job is now limited to the
size specified by the machine ClassAd attribute VirtualMemory
for the slot that the job is running on.
(Ticket #4417).
The new configuration variable COLLECTOR_PORT specifies
the default port used by the condor_collector daemon and command line tools.
The default value is 9618.
This default is the same port as has been used in previous HTCondor versions.
(Ticket #4432).
The condor_shared_port daemon will now work
if the default location given by configuration variable
DAEMON_SOCKET_DIR, which is $(LOCK)/daemon_sock,
is longer than 90 characters in length.
On Linux platforms, abstract sockets are now the primary method for
condor_shared_port to forward an incoming connection to the intended
daemon.
(Ticket #4465).
The use of a single log file to write events and enforce the
dependencies of a DAG represented by a condor_dagman instance is mandatory.
To implement this,
the -dont_use_default_node_log command-line
option to condor_submit_dag is disabled,
and an attempt to set configuration variable
DAGMAN_ALWAYS_USE_NODE_LOG to False will generate an
error.
(Ticket #3994).
The new condor_dagman configuration variable
DAGMAN_SUPPRESS_JOB_LOGS allows users to prevent DAG node
jobs from writing to the log file specified in their submit description file.
See section 3.3.25 for details.
(Ticket #4353).
New special variables @(OWNER) and @(NODE_NAME) are
available when defining configuration variable
DAGMAN_DEFAULT_NODE_LOG.
These values make it easier to avoid log file name collisions.
(Ticket #4334).
condor_submit will no longer insert an OpSys requirement
for a job
when one of OpSysAndVer, OpSysLongName, OpSysName,
or OpSysShortName is already specified by the user in
the Requirements expression of the submit description file.
(Ticket #4519).
The configuration file $(HOME)/.condor/condor_config
is no longer considered for the single, initial, global configuration file.
Instead, a user-specific configuration file has been added as the
last file parsed.
The new configuration variable USER_CONFIG_FILE may change the
default file name or disable this feature.
Section 3.3.1 describes the ordering
in which configuration files are parsed.
(Ticket #3158).
Daemons now authenticate many client nework connections in
parallel, rather than one at a time.
This improves the scalability of daemons that receive many client
connections, like the condor_schedd and condor_collector.
The improvement is most noticeable when using the FS and GSI
authentication methods.
(Ticket #4137).
The GSI security libraries are now loaded into memory only when GSI
authentication is required.
This reduces memory usage when GSI authentication is not used.
The memory reduction will be most noticeable when there are many
condor_shadow processes running.
(Ticket #4483).
Implemented fine-grained locking in the HTCondor python module to
allow other python threads to run during HTCondor calls.
(Ticket #4507).
Bugs Fixed:
None.
Version 8.3.0
Release Notes:
HTCondor version 8.3.0 released on August 12, 2014.
This release contains all improvements and bug fixes from
HTCondor version 8.2.2.
New Features:
When a daemon creates a child daemon process, it also creates a
security session shared with the child daemon.
This makes the initial communication between the daemons more efficient.
(Ticket #4405).
Negotiation cycle performance has been improved, especially
over a wide-area network, by reducing network traffic and latency
between a submit machine and a central manager.
The new configuration variable
NEGOTIATOR_RESOURCE_REQUEST_LIST_SIZE
does performance tuning, as defined
in section 3.3.17.
(Ticket #4460).
The synchronization of the job event log was improved by only
using fsync() where necessary and
fdatasync() where sufficient.
This should provide a small reduction in disk I/O to
the condor_schedd daemon.
(Ticket #4283).
CPU usage by the condor_collector has been reduced when
handling normal queries from condor_status,
and CPU usage by the condor_schedd has been reduced when
handling normal queries from condor_q.
(Ticket #4448).
HTCondor can now internally cache the result of Globus authorization
callouts.
The caching behavior is enabled by setting configuration variable
GSS_ASSIST_GRIDMAP_CACHE_EXPIRATION to a non-zero value.
This feature will be useful for sites that use the Globus authorization
callouts based only on DN and VOMS FQAN, and for sites that have
performance issues.
(Ticket #4138).
The job ClassAd attribute DAG_Status is included in
the dagman.out file.
(Ticket #4381).
The new -DoRecovery command line option for condor_dagman
and condor_submit_dag causes condor_dagman to run in
recovery mode.
(Ticket #2218).
The new -ads option to condor_status permits a set of ClassAds
to be read from a file, processing the ClassAds as if they came from
the condor_collector.
(Ticket #4414).
Daemon ClassAd hooks implementing Startd Cron functionality
can now return multiple ClassAds,
and the hooks can specify which ClassAds their output should merge into.
(Ticket #4398).
Two new condor_schedd ClassAd statistics attributes are
available: JobsRunning and JobsAccumExceptionalBadputTime.
(Ticket #4409).
Bugs Fixed:
Fixed a bug that caused condor_dagman to unnecessarily attempt
to read node job submit description files,
which could cause spurious warnings when in recovery mode.
Strictly speaking, the bug is fixed only for the
default case in which DAGMAN_ALWAYS_USE_NODE_LOG is set
to True.
(Ticket #3843).
Fixed a bug in the condor_schedd daemon that caused the values
of the ClassAd attributes JobsRunningSizes and
JobsRunningRuntimes to be much larger than they should have been.
(Ticket #4409).