Cloudera Enterprise 5.5.4 Released

[#1]

We are pleased to announce the release of Cloudera Enterprise 5.5.4 (CDH 5.5.4, Cloudera Manager 5.5.4, and Cloudera Navigator 2.4.4).  

This release fixes key bugs and includes the following:

• CDH fixes for the following issues:

• FLUME-2886 - Optional Channels can cause OOMs

• HADOOP-12718 - Incorrect error message by fs -put local dir without permission

• HDFS-9406 - FSImage may get corrupted after deleting snapshot

• HDFS-9514 - TestDistributedFileSystem.testDFSClientPeerWriteTimeout failing; exception being swallowed

• HDFS-9701 - DN may deadlock when hot-swapping under load

• HBASE-15234 The Replication Cleaner process can abort if its connection to ZooKeeper is inconsistent

• MAPREDUCE-6460 - TestRMContainerAllocator.testAttemptNotFoundCausesRMCommunicatorException fails

• MAPREDUCE-6528 - Memory leak for HistoryFileManager.getJobSummary()

• YARN-3446 - FairScheduler headroom calculation should exclude nodes in the blacklist

• HBASE-15019 - Replication stuck when HDFS is restarted

• HIVE-10303 - HIVE-9471 broke forward compatibility of ORC files

• HIVE-13065 - Hive throws NPE when writing map type data to an HBase backed table

• HIVE-13243 - Hive drop table on encryption zone fails for external tables

• HIVE-13401 - Kerberized HS2 with LDAP auth enabled fails Kerberos/delegation token authentication

• HUE-3132 - [core] Fix Sync LDAP users and groups for anonymous binds

• IMPALA-2592 - DataStreamSender::Channel::CloseInternal() does not close the channel on an error

• IMPALA-2599 - Pseudo-random sleep before acquiring Kerberos ticket possibly not really pseudo-random

• IMPALA-2711 - Fix memory leak in Rand()

• IMPALA-2719 - test_parquet_max_page_header fails on Isilon

• IMPALA-3095 - Add configurable whitelist of authorized internal principals

• KITE-1114 - Kite CLI json-import HDFS temp file path not multiuser safe, fix missing license header

• OOZIE-2419 - HBase credentials are not correctly proxied

• SENTRY-1044 - Tables with non-HDFS locations break HMS startup

• SOLR-8215 - Only active replicas should handle incoming requests against a collection

• SPARK-10914 - UnsafeRow serialization breaks when two machines have different Oops size

• SPARK-12617 - [PYSPARK] Move Py4jCallbackConnectionCleaner to Streaming, clean up the leak sockets of Py4J

• SQOOP-2847 - Sqoop --incremental + missing parent --target-dir reports success with no data

For a full list of upstream JIRAs fixed in CDH 5.5.4, see the issues fixed section of the Release Notes.

• Cloudera Manager fixes for the following issues:

• Kafka MirrorMaker would not start when Kafka was installed using packages. This occurred because KAFKA_HOME was not set to the correct default when starting MirrorMaker. This issue affected Cloudera Manager 5.4.0 and higher with Kafka 1.4.0 and higher.
• When Sentry Sync is enabled, new Hive tables failed to replicate. Replication now occurs as expected.
• In previous releases, Cloudera Manager SAML metadata was missing an alias and signature. As a result, errors sometimes occur when logging out.
• In some cases, provisioning of a cluster may fail at the start of the process. This does not happen in all cases and is mainly noticed on RHEL 6 and especially when some hosts are reporting bad health. Parcel activation and first run command now complete as expected, even when some hosts report bad health.

For a full list of issues fixed in Cloudera Manager 5.5.4, see the issues fixed section of the Release Notes.

• Issues Fixed in Cloudera Navigator 2.4.4
• Lineage does not render on MacOS using Chrome 48.0.2564.109. After upgrade to 2.4.x, only entries related to deleted files are visible.

For full list of issues fixed in Cloudera Navigator 2.4.4, see the issues fixed section of the Release Notes.

• Issues Fixed in Key Trustee KMS 5.5.4
• If the Key Trustee KMS 5.5.0 parcel is deactivated, any existing GPG keys are also deactivated. If the parcel is then reactivated, new GPG keys (used to create an authenticated and private communication channel with the Key Trustee Server) are generated. The existing GPG keys that were in use before the deactivation are not lost; however, they become inactive. If remedial action is not taken before deactivation, this can result in a loss of access to HDFS Encryption Zone keys generated with the older set of GPG keys. This in turn leads to loss of access to all data in all encryption zones. As long as the Key Trustee KMS parcel directory is not deleted, access can be restored. Assistance from Cloudera Support may be required. See TSB 2016-121 for more information (requires login to the Cloudera Support Portal).
• The UNDELETE and PURGE ACL entries were being read from kms-site.xml instead of kms-acls.xml.

For full list of issues fixed in Key Trustee KMS 5.5.4, see the issues fixed section of the Release Notes.

We look forward to you trying it, using the information below:

• Download Cloudera Enterprise

• View the documentation

As always, we are happy to hear your feedback. Please send your comments and suggestions to the user group or through our community forums. You can also file bugs through our external JIRA projects on issues.cloudera.org.