Product Announcements
Find the latest product announcements and version updates

[ANNOUNCE] Cloudera Enterprise 5.5.2 and Cloudera Manager 5.5.3 Released

Expert Contributor

On February 9th, 2016,  we announced the release of Cloudera Enterprise 5.5.2. Shortly after that, we discovered a severe bug in Cloudera Manager 5.5.2, so we decided to remove the release. CDH 5.5.2 was not affected by this bug.

 

Today we are releasing CDH 5.5.2, Cloudera Manager 5.5.2 and Cloudera Manager 5.5.3. All improvements, fixes, and changes in Cloudera Manager 5.5.2, as well as a change related to LDAP authentication, are included in Cloudera Manager 5.5.3. If you are upgrading from a previous version of Cloudera Manager, Cloudera recommends that you upgrade to version 5.5.3 or higher.  

 

This release fixes key bugs and includes the following:

  • CDH fixes for the following issues:
    • (HBase) RegionCoprocessorHost System.nanoTime() performance bottleneck.
    • (Hadoop) Exception may be swallowed in KMSClientProvider.
    • (HDFS) Fix the TestDFSUpgradeWithHA due to BindException.
    • (HDFS) Replication violates block placement policy.
    • (HDFS) HttpFS does not parse ACL syntax correctly for operation REMOVEACLENTRIES.
    • (HDFS) Possible NullPointerException in BlockManager if no excess replica can be chosen.
    • (MapReduce) Multibyte delimiters with LineRecordReader cause duplicate records.
    • (Yarn) Resource manager fails with NullPointerException.
    • (HBase) VerifyReplication should not mask the exception during result comparison.
    • (Hive) 'hadoop.proxyuser.hive.groups' configuration does not prevent an unauthorized user from accessing metastore.
    • (Hive) Exception on HBaseSerDe.serialize binary field.
    • (Impala) Throw AnalysisError if table properties are too large.
    • (Impala) Re-enable SSL and Kerberos on server-server.
    • (Oozie) Kerberos credentials can expire if the KDC is slow to respond.

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

  • Cloudera Manager 5.5.2 fixes for the following issues:
    • Cross-site scripting vulnerability using malformed strings in the parcel remote URL list.
    • In secure clusters, DataNode fails to start when dfs.data.transfer.protection is set and DataNode ports changed to unprivileged ports.
    • Updating the Hive NameNode location multiple times could lead to data corruption.
    • Cloudera Manager skips NameNode logs in the diagnostic bundle.
    • Kafka 2.0 fails to deploy on large clusters because reserved.broker.max.id defaults to 1000.
    • Spark REST API does not work when parcels are used.
    • Update Apache Commons Collections library in Cloudera Manager due to major security vulnerability.
    • Oozie keystore and truststore passwords not redacted.

 

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

  • Cloudera Manager 5.5.3 fixes for the following issue:
    • When upgrading to Cloudera Manager 5.5.2 from versions 5.4.8 or earlier, customers who have non-read-only roles configured through LDAP, and who have not explicitly set Cloudera Manager local roles, may lose their Cloudera Manager administration privileges.

 

All improvements, fixes, and changes in Cloudera Manager 5.5.2, as well as a change related to LDAP authentication, are included in Cloudera Manager 5.5.3. For more details, see the issues fixed section of the Release Notes.

  • Cloudera Navigator 2.4.2 fixes for the following issues:
    • After upgrade, entities are incorrectly marked as deleted.
    • When Navigator uses the Cloudera Manager authenticator and Cloudera Manager is TLS enabled, authentication fails.
    • Policies created from the Analytics UI were not working.

 

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

 

  • In the Cloudera Navigator 2.4.3 release, there are no new features or fixed issues.

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.

 

0 REPLIES 0