Next: 10.4 Development Release Series
Up: 10. Version History and
Previous: 10.2 Upgrading from the
Contents
Index
Subsections
10.3 Stable Release Series 8.4
This is a stable release series of HTCondor.
As usual, only bug fixes (and potentially, ports to new platforms)
will be provided in future 8.4.x releases.
New features will be added in the 8.5.x development series.
The details of each version are described below.
Version 8.4.2
Release Notes:
- HTCondor version 8.4.2 released on November 17, 2015.
New Features:
- condor_history no longer reports an error when run on a system that does
not have a history file.
This change was made because the history file is not created until after the
first job runs.
So, users were always seeing an error message on a fresh installation of
HTCondor.
(Ticket #5374).
Bugs Fixed:
- Fixed a bug introduced in 8.4.1 that could cause the condor_schedd
to exit.
This affected remote submit, HTCondor-CE, and HTCondor-C.
(Ticket #4522).
- The TCP_FORWARDING_HOST is now honored by
HTCondor client programs.
(Ticket #5339).
- Fixed a problem where Standard Universe jobs could not restart
from a checkpoint in the Enterprise Linux 6 RPM distribution.
(Ticket #5382).
(Ticket #5383).
- Fixed bugs in the function of the DAGMan
DAGMAN_MAX_JOBS_IDLE/-maxidle throttle,
especially for node jobs that create multiple procs.
(Ticket #5333).
- Fixed a problem where the RPMs would claim to publicly provide
Globus shared libraries that are in a private location.
(Ticket #5349).
- Added a default request_memory for condor_submit -interactive
of 512 megabytes. Formerly, the default was one, which is
insufficient in environments that strictly enforce memory
usage.
(Ticket #5344).
- Fixed a problem were the condor_classad RPM would claim to
provide a replacement for the classad RPM in EPEL.
(Ticket #5400).
- HTCondor now applies the configuration settings
GRIDMANAGER_GAHP_CALL_TIMEOUT and
GRIDMANAGER_CONNECT_FAILURE_RETRY_COUNT
when running grid universe jobs for EC2 or Google Compute Engine.
(Ticket #5300).
- Fixed a crash in the condor_schedd that happened when the
schedd was under load and being shutdown in the fast mode.
(Ticket #5371).
- Added a timeout to the condor_fetchlog command so that it
will not hang forever waiting for a unresponsive daemon.
(Ticket #5325).
- Fixed a problem that prevented HTCondor from building on some 64-bit Linux
platforms such as Arm64.
This was reported by Debian maintainers as their Bug 804386.
(Ticket #5380).
- Fixed a problem where the platform string was incorrect in the RPM
packages.
(Ticket #5384).
Known Issues:
- The DAGMan workflow log file is not correctly written for local
universe DAG node jobs that have no log file specified in the submit file,
which causes DAGMan to wait forever, thinking the jobs have not completed.
Note that this problem can be worked around by specifying any
log file for the job, even log = /dev/null.
(This bug is a regression that was introduced some time since version
8.2.4.)
(Ticket #5299).
- DAG node retries do not work correctly with DAG node submit files
that create more than one proc in the resulting cluster (such nodes
cause DAGMan to hang if the retry is activated).
We believe that this bug has existed since DAGMan first supported
multi-proc node jobs.
(Ticket #5350).
Version 8.4.1
Release Notes:
- HTCondor version 8.4.1 released on October 27, 2015.
Known Issues:
- Remote submit to an 8.4.1 condor_schedd is broken if file transfer is
used. This also means HTCondor-CE and HTCondor-C are broken. This bug will
be fixed in version 8.4.2.
(Ticket #4522).
- TCP_FORWARDING_HOST is disregarded by HTCondor clients
starting in version 8.3.6. This bug will be fixed in version 8.4.2 and 8.5.1.
(Ticket #5339).
New Features:
- Added support to allow an admin to always volume mount
certain directories into docker universe containers running
on a host.
(Ticket #5308).
- Added four policy metaknobs to simplify configuring a policy
to either preempt or hold jobs that use more memory
or CPU cores than provisioned in the slot. See the POLICY
category of metaknobs in section 3.3.1 for
additional information.
(Ticket #5250).
- Added configuration variables and documentation so that we uniformly prefer
<var>_ATTRS over <var>_EXPRS but support both. This includes
STARTD_ATTRS, STARTD_JOB_ATTRS and SUBMIT_ATTRS
which are often used by HTCondor sites which customize the configuration. These
configuration variables are now exclusively for use by HTCondor administrators;
The former default values for these variables have been moved into other configuration
which is reserved for use by HTCondor developers. This is done to prevent administrators
from accidentally removing the necessary defaults.
A warning about use of STARTD_EXPRS has been disabled unless
STARTD_ATTRS or SLOT_TYPE_<n>_STARTD_ATTRS is also used, since
the use all three of these at the same time is not supported.
(Ticket #5326).
- When condor_reconfig and condor_restart are run as root
they will check to see if the condor user has read access to all of the
configuration files before sending the command. This is done to prevent aborting the daemons
accidentally by sending reconfig after the admin creates a new config file and
forgets to give the condor user read access to that file.
(Ticket #4506).
- Added the -natural sort option to condor_status to sort the slots
in numerical order rather than alphabetical order.
(Ticket #5131).
Bugs Fixed:
Version 8.4.0
Release Notes:
- HTCondor version 8.4.0 released on September 14, 2015.
New Features:
Bugs Fixed:
- Fixed a bug introduced in HTCondor version 8.3.7 that caused the
condor_shared_port daemon to leak file descriptors.
Also made HTCondor work better when some HTCondor daemons
are using shared port, but the condor_master is not.
(Ticket #5259).
- The condor_starter lowers the OOM (out of memory) score of jobs
so the OOM killer is more likely to chose an HTCondor job rather than
an HTCondor daemon or other user process.
(Ticket #5249).
- Job submission fails if X.509 certificates are advertised with EC2
grid universe jobs.
Therefore EC2 grid universe jobs no longer advertise their access keys.
(Ticket #5252).
Next: 10.4 Development Release Series
Up: 10. Version History and
Previous: 10.2 Upgrading from the
Contents
Index