Reply
Cloudera Employee
Posts: 27
Registered: ‎08-29-2016

[ANNOUNCE] Cloudera Enterprise 5.8.2 Released

Dear CDH, Cloudera Manager, and Cloudera Navigator users,

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

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
    • HBASE-15496 - Throw RowTooBigException only for user scan/get
    • HDFS-9137 - DeadLock between DataNode#refreshVolumes and BPOfferService#registrationSucceeded
    • HDFS-10525 - Fix NPE in CacheReplicationMonitor#rescanCachedBlockMap
    • HIVE-14006 - Hive query with UNION ALL fails with ArrayIndexOutOfBoundsException
    • IMPALA-3646 - Handle corrupt RLE literal or repeat counts of 0
    • IMPALA-3820 - Handle linkage errors while loading Java UDFs in Catalog
    • SPARK-16106 - [CORE] TaskSchedulerImpl should properly track executors added to existing hosts
    • SQOOP-2999 - Sqoop ClassNotFoundException (org.apache.commons.lang3.StringUtils) is thrown when executing Oracle direct import map task
    • YARN-4866 - FairScheduler: AMs can consume all vcores leading to a livelock when using FAIR policy

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

  • Cloudera Manager fixes for the following issues:
    • XSS in Kerberos activation: In lower releases, there was an XSS vulnerability on the Kerberos page. This is now fixed.
    • Oozie first run fails with custom principals: In 5.8.1, Oozie first run fails if using kerberos custom principals. This is now fixed.
    • Cluster export fails when service configuration is invalid: The export cluster template code path was failing because of stale configuration in the Cloudera Manager database. Having a stale configuration in the database is possible. This could happen when configurations are deprecated on older CDH releases.
    • Impala Breakpad script does not convert exponentials into decimals and leads to errors: Impala Breakpad script failure that happens when trying to collect more than 10 MB of dumps from a single role is fixed.
    • Agent orphan cleanup removes process dir from in flight process: With this fix, the preventative steps in TSB-181 are no longer required.

 

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

 

  • Cloudera Navigator fixes for the following issues:
    • Google analytics might not load if Navigator is served over https/ssl
    • Lineage Options and Search items are missing


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

  • Issues Fixed in Key Trustee KMS 5.8.2
    • KMS does not fail over 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.8.2, 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.

Announcements