10-04-2016 04:26 PM
We are pleased to announce the release of Cloudera Enterprise 5.7.4 (CDH 5.7.4, Cloudera Manager 5.7.4, Cloudera Navigator 2.6.4, and Key Trustee KMS 5.7.4).
This release fixes key bugs and includes the following:
CDH fixes for the following issues:
HADOOP-8436 - NPE In getLocalPathForWrite ( path, conf ) when the required context item is not configured
HDFS-8269 - getBlockLocations() does not resolve the .reserved path and generates incorrect edit logs when updating the atime
HDFS-9781 - FsDatasetImpl#getBlockReports can occasionally throw NullPointerException
MAPREDUCE-6628 - Potential memory leak in CryptoOutputStream
HBASE-16284 - Unauthorized client can shutdown the cluster
HIVE-14436 - Hive 1.2.1/Hitting "ql.Driver: FAILED: IllegalArgumentException Error"
HIVE-14743 - ArrayIndexOutOfBoundsException - HBASE-backed views query with JOINs
IMPALA-3682 - Do not retry unrecoverable socket creation errors
IMPALA-4020 - Handle external conflicting changes to HMS gracefully
SPARK-8428 -Fix integer overflows in TimSort
For a full list of upstream JIRAs fixed in CDH 5.7.4, see the issues fixed section of the Release Notes.
Cloudera Manager fixes for the following issues:
Agent orphan cleanup removes process dir from in flight process
Host inspector incorrectly warns about kernel version "2.6.32-504.16.2"
If total_space_bytes is really big, heartbeats fail
Oozie points to older sharelib even after running sharelib install command
OOMKiller script does not work for Impala Catalog
For a full list of issues fixed in Cloudera Manager 5.7.4, see the issues fixed section of the Release Notes.
Issues Fixed in Key Trustee KMS
KMS does not failover to Passive Key Trustee Server in some network failure scenarios: In some situations, if the Active Key Trustee Server is unreachable on the network, Key Trustee KMS does not fail over to the Passive Key Trustee Server.
For a full list of issues fixed in Key Trustee KMS 5.7.4, see the issues fixed section of the Release Notes.
We look forward to you trying it, using the information below:
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.