Dear CDH, Cloudera Manager, Impala, and Cloudera Navigator users,
We are pleased to announce the release of Cloudera Enterprise 5.3.3 (CDH 5.3.3, Cloudera Manager 5.3.3, and Cloudera Navigator 2.2.3).
Cloudera Enterprise 5.3.3
This release fixes key bugs and includes the following.
-
CDH
-
Replacing DataNode Disks or Manually changing the Storage IDs of Volumes in a Cluster may result in Data Loss. Fixed as part of HDFS-7575, HDFS-7596, HDFS-7960 and HDFS-7208.
-
Fixes to address issues with load balancing, loading ACLs, and integration with Hive in KMS
-
LDAP-related usability fixes in Hue
-
Bug fixes to handle Kerberos ticket validity, NameNode restarts, white spaces in ACLs, and other issues in Sentry
-
Index corruption during replication and other fixes in Search
-
Fixes for application recovery and ApplicationMaster tracking URL in high availability mode and other issues in YARN
-
Fixes to handle reliability, race conditions, memory leaks, and ACL handling in Impala
-
Several bug fixes in Hive to address usability and integration with KMS and YARN
-
Bug fixes in HBase and Sqoop
For full list of upstream JIRAs fixed in CDH 5.3.3, please see the Known issues fixed section of the Release Notes.
-
Cloudera Manager
-
The default value of the hive.metastore.client.socket.timeout property has changed to 60 seconds.
-
The property hadoop.ssl.enabled is deprecated. Cloudera Manager has been updated to use either dfs.http.policy or yarn.http.policy properties instead.
-
Cloudera Manager no longer requires you to restart your cluster after changing the Service Monitor Client Config Overrides property for a service.
-
After updating to a new release, Cloudera Manager incorrectly replaced the specified cluster name with cluster. Cloudera Manager now uses the correct cluster name.
-
Migration of client configuration data is now more robust with handling null host_id.
-
The property hive.log.explain.output is known to create instability of Cloudera Manager Agents in some specific circumstances, especially when Hive queries generate extremely large EXPLAIN outputs. Therefore, the property has been hidden from Cloudera Manager configuration screens. You can still configure the property by using advanced configuration snippets.
-
Starting new ZooKeeper Servers shortly after adding them no longer causes ZooKeeper data loss when the number of new servers exceeds the number of old servers.
-
Cloudera Navigator
We look forward to you trying it out, 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.
