Dear CDH, Cloudera Manager, and Cloudera Navigator users,
We are pleased to announce the release of Cloudera Enterprise 5.9.3 (CDH 5.9.3, Cloudera Manager 5.9.3, and Cloudera Navigator 2.8.3).
This release fixes key bugs and includes the following:
- CDH fixes for the following issues:
- HIVE-11418 - Dropping a database in an encryption zone with CASCADE and trash enabled fails
- HIVE-14380 - Queries on tables with remote HDFS paths fail in "encryption" checks.
- HIVE-14564 - Column Pruning generates out of order columns in SelectOperator which cause ArrayIndexOutOfBoundsException
- HIVE-16660 - Not able to add partition for views in hive when sentry is enabled
- IMPALA-5355 - Sentry Privileges and roles updated in the wrong order on impala restart
- IMPALA-5193 - Impala reads gzip compressed text as binary when skip.header.line.count > 0
- IMPALA-5197 - Parquet scan may incorrectly report "Corrupt Parquet file" in the logs
- IMPALA-4293 - Query profile should include error log
For a full list of upstream JIRAs fixed in CDH 5.9.3, see the issues fixed section of the Release Notes.
- Cloudera Manager fixes for the following issues:
- Low watermark value for Memstore Flush default is incorrect: For CDH versions 5.8 and higher, the Low Watermark for Memstore Flush configuration parameter is associated with the HBase parameter hbase.regionserver.global.memstore.lowerLimit. This value represents the fullness threshold of the memstore as a percentage of memstore capacity. The default value for this parameter was incorrectly set too low at .38. This can cause severe under utilization of the memstore. The default has been corrected to be .95. When upgrading to a version of Cloudera Manager with this fix, if the value was previously set to the old default of .38, it will automatically be increased to the new default, which may cause Cloudera Manager to mark your HBase service as having a stale configuration, requiring a restart. Additionally, if an existing Low Watermark for Memstore Flush configuration parameter has a value <= .9, it will be flagged as a configuration warning.
- Make Oozie Load-balancer URL mandatory when enabling Oozie HA: Fixed an issue when the Oozie Load Balancer field in the Oozie configuration is not set and Oozie high availability is in use (two or more Oozie Server roles are reployed). This now creates a validation error and Cloudera Manager does not let you start or restart Oozie until the problem is fixed.
For a full list of issues fixed in Cloudera Manager 5.9.3, see the issues fixed section of the Release Notes.
For a full list of issues fixed in Cloudera Navigator 2.8.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.
