Dear CDH, Cloudera Manager, and Cloudera Navigator users,
We are pleased to announce the release of Cloudera Enterprise 5.8.3 (CDH 5.8.3, Cloudera Manager 5.8.3, and Cloudera Navigator 2.7.3).
This release fixes key bugs and includes the following:
- CDH fixes for the following issues:
- HADOOP-13558 - UserGroupInformation created from a Subject incorrectly tries to renew the Kerberos ticket
- HBASE-16699 - Overflows in AverageIntervalRateLimiter's refill() and getWaitInterval()
- HDFS-8224 - Schedule a block for scanning if its metadata file is corrupt
- HIVE-10965 - Direct SQL for stats fails in 0-column case
- HUE-4891 - An unprivileged user can list document items
- IMPALA-4135 - Thrift threaded server times out connections during high load
- MAPREDUCE-6628 - Potential memory leak in CryptoOutputStream
- SPARK-12941 - Spark-SQL JDBC Oracle dialect fails to map string datatypes to Oracle VARCHAR datatype
- SQOOP-3021 - ClassWriter fails if a column name contains a backslash character
- YARN-4940 - yarn node -list -all fails if RM starts with decommissioned node
For a full list of upstream JIRAs fixed in CDH 5.8.3, see the issues fixed section of the Release Notes.
- Cloudera Manager fixes for the following issues:
- If total_space_bytes is very large, heartbeats fail.
- Cloudera Manager blocks HiveServer2 from enabling both LDAP and Kerberos authentication.
- [api] Latest Cloudera Manager Java client does not work on older versions of Cloudera Manager.
- Sentry Upgrade command is not retriable.
- OOMKiller script does not work for Impala Catalog.
For a full list of issues fixed in Cloudera Manager 5.8.3, see the issues fixed section of the Release Notes.
- Cloudera Navigator fixes for the following issues:
- Incomplete query strings in Navigator metadata: storing more than 32K characters in Solr causes an exception. Navigator now truncates any field longer than 32K to prevent the exception.
For a full list of issues fixed in Cloudera Navigator 2.7.3, 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.
