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

[ANNOUNCE] Cloudera Enterprise 5.12.1 Released

Dear CDH, Cloudera Manager, and Cloudera Navigator users,

 

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

 

This release fixes key bugs and includes the following:

 

  • CDH fixes for the following issues:
    • IMPALA-5615 - Compute Incremental stats is broken for general partition expressions
    • IMPALA-5539 - Reading timestamps from Kudu are wrong with -use_local_tz_for_unix_ts
    • IMPALA-5582 - Sentry privileges assigned to objects defined in uppercase can get deleted from the catalog
    • IMPALA-5500 - Reduce catalog topic size when --compact_catalog_topic is enabled
    • IMPALA-5579 - GetSchemas throws IndexArrayOutOfBoundsException if a table can't be loaded
    • IMPALA-5616 - Add a new flag --enable_minidumps
    • IMPALA-5524 - NullPointerException during planning with DISABLE_UNSAFE_SPILLS=TRUE
    • HIVE-16845 - INSERT OVERWRITE a table with dynamic partitions on S3 fails with NPE
    • HIVE-13588 - NPE is thrown from MapredLocalTask.executeInChildVM
    • HIVE-12274 - Increase width of columns used for general configuration in the metastore.
    • HIVE-16291 - Hive fails when unions a parquet table with itself
    • HIVE-16930 - HoS should verify the value of Kerberos principal and keytab file before adding them to spark-submit command parameters
    • HIVE-17050 - Multiline queries that have comment in middle fail when executed via "beeline -e"

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

 

  • Cloudera Manager fixes for the following issues:
    • Proper termination and cleanup of YARN applications during decommissioning: Fixed an issue where YARN applications may not exit gracefully or clean-up properly if hosts are decommissioned while application containers are still running. This could lead to unexpected container/application failure and/or orphaned container processes on YARN worker nodes. Now, when decommissioning a NodeManager or host running a NodeManager, Cloudera Manager first waits for the configured YARN graceful decommission timeout (if applicable), and allows additional time for ResourceManager to properly terminate the NodeManager and its child processes.
    • Spilled memory not populated in Impala queries and in the Spilled Memory tab in the Cluster Utilization report: Fixed an issue where the Memory Spilled metric for each Impala query was not correctly populated. This prevented various features that depend on this metric from functioning correctly. For example, the Spilled Memory tab of the Cluster Utilization Report was not populated with data. This is now fixed.
    • Threads CPU time and Total Time are not populated in Impala Query Monitoring: The Thread CPU Time and Total Time attributes of Impala Query Monitoring are now correctly populated.
    • Hue Load Balancer caused login failure: Fixed an issue where using Apache httpd 2.4 as the Hue load balancer caused Hue logins to fail when TLS is enabled for Hue. This change requires Cloudera Manager to set the use_x_forwarded_host parameter in the hue.ini file to "true". After upgrading Cloudera Manager, Cloudera Manager will report that the Hue Server and Load Balancer role configurations are stale. If your cluster is affected by this bug, you must restart the Hue service.
    • Exception thrown when searching log file: Fixes an issue where an exception might be thrown when searching a log when the log file size is larger than 2 GB.

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

 

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

 

We look forward to you trying the new release, 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