Thank you for choosing CDH, your download instructions are below:

Please Read and Accept our Terms

I accept the Terms of Cloudera's Standard License Agreement

Long term component architecture

As the main curator of open standards in Hadoop, Cloudera has a track record of bringing new open source solutions into its platform (such as Apache Spark, Apache HBase, and Apache Parquet) that are eventually adopted by the community at large. As standards, you can build longterm architecture on these components with confidence.

PLEASE NOTE:

With the exception of DSSD support, Cloudera Enterprise 5.6.0 is identical to CDH 5.5.2/Cloudera Manager 5.5.3 If you do not need DSSD support, you do not need to upgrade if you are already using the latest 5.5.x release.

System Requirements

What's New

Documentation

System Requirements

Supported Operating Systems

Supported Databases

Supported JDK Versions

Supported Browsers

Supported Internet Protocol

Supported Transport Layer Security Versions

Supported Operating Systems

Note: All CDH hosts that make up a logical cluster need to run on the same major OS release to be covered by Cloudera Support. Cloudera Manager needs to run on the same OS release as one of the CDH clusters it manages, to be covered by Cloudera Support. The risk of issues caused by running different minor OS releases is considered lower than the risk of running different major OS releases. Cloudera recommends running the same minor release cross-cluster, because it simplifies issue tracking and supportability.

Cloudera Enterprise is supported on platforms with Security-Enhanced Linux (SELinux) enabled. However, Cloudera does not support use of SELinux with Cloudera Navigator. Cloudera is not responsible for policy support nor policy enforcement. If you experience issues with SELinux, contact your OS provider.

Selected tab: SupportedOperatingSystems

Supported Databases

Component

MariaDB

MySQL

SQLite

PostgreSQL

Oracle

Derby - see Note 5

Cloudera Manager

5.5, 10

5.7, 5.6, 5.5, 5.1

–

9.4, 9.3, 9.2, 9.1. 8.4, 8.3, 8.1

12c, 11gR2

See Note 11

Oozie

5.5, 10

5.7, 5.6, 5.5, 5.1

–

9.4, 9.3, 9.2, 9.1. 8.4, 8.3, 8.1

See Note 3

12c, 11gR2

Default

Flume

–

–

–

–

–

Default (for the JDBC Channel only)

Hue

5.5, 10

5.7, 5.6, 5.5, 5.1

See Note 6

Default

9.4, 9.3, 9.2, 9.1. 8.4, 8.3, 8.1

See Note 3

12c, 11gR2

–

Hive/Impala

5.5, 10

5.7, 5.6, 5.5, 5.1

See Note 1

–

9.4, 9.3, 9.2, 9.1. 8.4, 8.3, 8.1

See Note 3

12c, 11gR2

Default

Sentry

5.5, 10

5.7, 5.6, 5.5, 5.1

See Note 1

–

9.4, 9.3, 9.2, 9.1. 8.4, 8.3, 8.1

See Note 3

12c, 11gR2

–

Sqoop 1

5.5, 10

See Note 4

–

See Note 4

See Note 4

–

Sqoop 2

5.5, 10

See Note 9

–

–

–

Default

Note:

Cloudera supports the databases listed above provided they are supported by the underlying operating system on which they run.

MySQL 5.5 is supported on CDH 5.1. MySQL 5.6 is supported on CDH 5.1 and higher. The InnoDB storage engine must be enabled in the MySQL server.

PostgreSQL 9.2 is supported on CDH 5.1 and higher. PostgreSQL 9.3 is supported on CDH 5.2 and higher. PostgreSQL 9.4 is supported on CDH 5.5 and higher.

For purposes of transferring data only, Sqoop 1 supports MySQL 5.0 and above, PostgreSQL 8.4 and above, Oracle 10.2 and above, Teradata 13.10 and above, and Netezza TwinFin 5.0 and above. The Sqoop metastore works only with HSQLDB (1.8.0 and higher 1.x versions; the metastore does not work with any HSQLDB 2.x versions).

Derby is supported as shown in the table, but not always recommended. See the pages for individual components in the Cloudera Installation guide for recommendations.

CDH 5 Hue requires the default MySQL version of the operating system on which it is being installed, which is usually MySQL 5.1, 5.5, or 5.6.

When installing a JDBC driver, only the ojdbc6.jar file is supported for both Oracle 11g R2 and Oracle 12c; the ojdbc7.jar file is not supported.

Sqoop 2 lacks some of the features of Sqoop 1. Cloudera recommends you use Sqoop 1. Use Sqoop 2 only if it contains all the features required for your use case.

MariaDB 10 is supported only on CDH 5.9 and higher.

For Oracle 12cR1, the Oracle 12 client library and the OJDBC7 connector are not supported.

Selected tab: SupportedDatabases

Supported JDK Versions

CDH and Cloudera Manager Supported JDK Versions

Only 64 bit JDKs from Oracle are supported. Oracle JDK 7 is supported across all versions of Cloudera Manager 5 and CDH 5. Oracle JDK 8 is supported in C5.3.x and higher.

A supported minor JDK release will remain supported throughout a Cloudera major release lifecycle, from the time of its addition forward, unless specifically excluded.

Supported Internet Protocol

Multihoming CDH or Cloudera Manager is not supported outside specifically certified Cloudera partner appliances. Cloudera finds that current Hadoop architectures combined with modern network infrastructures and security practices remove the need for multihoming. Multihoming, however, is beneficial internally in appliance form factors to take advantage of high-bandwidth InfiniBand interconnects.

Although some subareas of the product may work with unsupported custom multihoming configurations, there are known issues with multihoming. In addition, unknown issues may arise because multihoming is not covered by our test matrix outside the Cloudera-certified partner appliances.

Selected tab: SupportedInternetProtocol

Supported Transport Layer Security Versions

The following components are supported by the indicated versions of Transport Layer Security (TLS):

Hue

Apache Impala (incubating)

Apache Oozie

OOZIE-2225 In addition to the filter parameters name, user, group, status, frequency and unit, Oozie now supports a wild card parameter that matches a partial name, a partial user, or a complete ID.

For example, a query with text='asdf' would return all jobs that satisfy ANY of the following conditions.

job.name.contains(text)

job.user.contains(text)

job.id = text

Cloudera Search

The solrctl command can be run in debug mode using the --debug or --trace parameters.

YARN

Expose maxResources per user in YARN Dynamic Resource Pools

YARN Dynamic Resource Pools now supports default capacity limits (Max Resources) that automatically apply to all child pools of any resource pool. You can control the YARN resources available to any user or group on the cluster by configuring these settings on a parent pool, and then use placement rules to auto-create child pools per user or group.

UX improvements in the Pools page

Improvements include:

Every input row is now clickable and takes the user to that input field in the edit dialog.