Dear CDH, Cloudera Manager, and Cloudera Navigator users,
We are pleased to announce the release of Cloudera Enterprise 5.15.2 (CDH 5.15.2, Cloudera Manager 5.15.2, and Cloudera Navigator 2.14.2).
This release fixes key bugs and includes the following:
- The following upstream issues are fixed in CDH 5.15.2:
- HIVE-12981 - ThriftCLIService uses incompatible getShortName() implementation
- HUE-8487 - [useradmin] Fix Add Sync LDAP user fails when using DN with special character
- HUE-8467 - [jobbrowser] Support impala digest auth for queries
- HDFS-12299 - Fixed a race between update pipeline and DataNode Re-Registration.
- KUDU-2463 - Fixed an issue in which incorrect results would be returned in scans following a server restart.
For a full list of upstream JIRAs fixed in CDH 5.15.2, see the issues fixed section of the Release Notes.
- Cloudera Manager fixes for the following issues:
- Restart Warnings are incorrect after starting a role with an outdated configuration
- Upgrade to CDH 5.15.2 fails with CM 5.15.2 and OpenJDK
- Kafka JMX connections listen on all interfaces unnecessarily
- Flume uses default values for Kafka TLS settings
For a full list of issues fixed in Cloudera Manager 5.15.2, see the issues fixed section of the Release Notes.
- Cloudera Navigator fixes for the following issues:
- Connection timeout increased in Navigator Audit Server to avoid broken pipe errors
- Navigator Metadata Server failed to start with InvalidClassException, local class incompatible
- Navigator Metadata Server purge did not run at the scheduled time
- Support for PostgreSQL 10
- Navigator Metadata Server has high CPU usage, linking taking too long after Spark extraction
- ClassCastException in Navigator Metadata Server log
- Authentication fails with javax.naming.PartialResultException when using LDAP
For a full list of issues fixed in Cloudera Navigator 2.14.2, see the issues fixed section of the Release Notes.
We look forward to you trying the new release by 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.
