Reply
Posts: 354
Topics: 162
Kudos: 60
Solutions: 27
Registered: ‎06-26-2013

Announcing: Cloudera Enterprise 5.4.1 (CDH 5.4.1, Cloudera Manager 5.4.1, and Cloudera Navigator 2.3.1)

Dear CDH, Cloudera Manager, Impala, and Cloudera Navigator users,

 

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

 

Cloudera Enterprise 5.4.1

This release fixes key bugs and includes the following.

  • CDH

    • Optimization to avoid opening too many file descriptors during encryption

    • DistCp fix to handle copying to root directory

    • HDFS fixes for:

      • Edit log corruption when append fails with a quota violation.

      • Rolling upgrade restoring blocks from trash multiple times, which could cause. significant and unnecessary block churn.

      • NameNode failover during high availability (HA) upgrade, which can cause the DataNode to finalize the upgrade.

      • Null pointer exception (NPE) when NameNode transitions to active during startup.

      • Incorrectly allowing HA NameNode to start in secure mode with HTTP wildcard address configured.

      • Handling cache checks when encryption is enabled.

    • YARN fixes for handling a race condition in the localizer, headroom calculation in the fair scheduler, and delegation token handling with DistCp.

    • MapReduce fixes to handle heap sizes greater than 2 GB when expressed in bytes, MR2 regression from MR1 for running local jobs with -libjars command options, and hung jobs in certain scenarios.

    • Minor HBase user interface and usability improvements, scanner improvements when not all values are returned, improved resource utilization in scanners, fixes to handle a broken truncate_preserve command in HBase shell, and deletion of HFiles used by a table cloned from a snapshot when that snapshot is deleted.

    • Fixes for HiveServer2 memory leaks, column access for Parquet files, delegation token handling errors, and Hive on Spark bugs in Hive.

    • Hue fixes for handling the correct number of rows with Hive queries returning data not encoded properly, errors during Oozie fork creation in the workflow editor, and Impala explain button.

    • Fixes to handle crashes and errors with analytical functions, crashes due to missing newline at the end of the file and aggregate functions with empty select-project-join would crash

    • Oozie automatically sets configurations so that Spark jobs are shown in the Spark History Server.

    • Fixes for a memory leak with HiveServer2 integration, performance improvement in metastore plugin cache initialization, and other bug fixes in Sentry.

    • Several bug fixes in Solr.

    • Fixes in Spark to make Python support more usable with YARN, and to handle thread leaks and synchronization issues.

    • Valid Avro column name generation and other bug fixes in Sqoop.

    • Fix to handle crashes due to malformed packets and improved client-side logging in ZooKeeper

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

  • Cloudera Manager

    • Oozie HA plugin is now configured by Cloudera Manager.

    • Enabling wildcarding in a secure environment no longer causes the NameNode to fail to start.

    • Support for adding Hue with HA.

    • Clicking the "Revert to default" icon stores the default value as a user-defined value in the new configuration pages.

    • Logging of command unavailable messages is improved.

    • Various HDFS role migration improvements.

    • HDFS/Hive replication no longer fails when replicating to a target cluster that runs CDH 4 and has Kerberos enabled.

  • Cloudera Navigator fixes for the following issues:

    • Link disappears when expanded.

    • Operations on canary files should be filtered out.

    • Hive views have same icon as Hive fields in lineage.

    • Facet count should show (0) instead of (-) when there are no matching entities.

    • Column lineage does not display.

    • Kite dataset extraction fails when HDFS HA is enabled.

    • Sentry auditing does not work if the Python version is lower than 2.5.

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.

Announcements