Your browser is out of date!

Update your browser to view this website correctly. Update my browser now

×

Easily Manage Hadoop in Production

Cloudera Manager makes it easy to manage Hadoop deployments of any scale in production. Quickly deploy, configure, and monitor your cluster through an intuitive UI - complete with rolling upgrades, backup and disaster recovery, and customizable alerting.

 

Cloudera Manager is available as an integrated and supported part of Cloudera Enterprise.

Cloudera Manager 5.1.0



The recommended tool for installing Cloudera Enterprise

This download installs Cloudera Enterprise or Cloudera Express.

 

Cloudera Enterprise requires a license; however, when installing Cloudera Express you will have the option to unlock Cloudera Enterprise features for a free 60-day trial.

 

Once the trial has concluded, the Cloudera Enterprise features will be disabled until you obtain and upload a license.

Thank you for choosing Cloudera Manager, your download instructions are below:

Instructions for Installing Previous Cloudera Manager Versions

 

To install any previous version of Cloudera Manager 5, you must create a custom repository for the RPM or DEB Files.

See the instructions in Installing Older Versions of Cloudera Manager 5.

The download locations of the 5.0.x RPM or DEB Files are listed in Cloudera Manager Version and Download Information.

Sign in or complete our product interest form to continue.

Please Read and Accept our Terms

Supported Operating Systems

 

Cloudera Manager supports the following operating systems:

  • RHEL-compatible systems
    • Red Hat Enterprise Linux and CentOS 5.7, 64-bit
    • Red Hat Enterprise Linux and CentOS 6.4, 64-bit
    • Red Hat Enterprise Linux and CentOS 6.4 in SE Linux Mode
    • Red Hat Enterprise Linux and CentOS 6.5, 64-bit
    • Oracle Enterprise Linux 5.6 (UEK R2), 64-bit
    • Oracle Enterprise Linux 6.4 (UEK R2), 64-bit
    • Oracle Enterprise Linux 6.5 (UEK R2, UEK R3), 64-bit
  • SLES - SUSE Linux Enterprise Server 11, 64-bit. Service Pack 2 or later is required for CDH 5 and Service Pack 1 or later is required for CDH 4. To use the embedded PostgreSQL database that is installed when you follow Installation Path A - Automated Installation by Cloudera Manager, the Updates repository must be active. The SUSE Linux Enterprise Software Development Kit 11 SP1is required on hosts running the Cloudera Manager Agents.
  • Debian - Debian 7.0 and 7.1, 6.0 (deprecated), 64-bit
  • Ubuntu - Ubuntu 12.04, 10.04 (deprecated), 64-bit

Note:

  • Debian 6.0 and Ubuntu 10.04 are supported only for CDH 4.
  • Using the same version of the same operating system on all cluster hosts is strongly recommended.

 

 

 

Selected tab: SupportedOperatingSystems

Supported JDK Versions

 

Cloudera Manager supports Oracle JDK 1.7.0_55 when it's managing CDH 5.x and Oracle JDK 1.6.0_31 and 1.7.0_55 when it's managing CDH 4.x. Cloudera Manager supports Oracle JDK 1.7.0_55 when it's managing both CDH 4.x and CDH 5.x clusters. Oracle JDK 1.6.0_31 and 1.7.0_55 can be installed during the installation and upgrade. For further information, see Java Development Kit Installation.

 

 

 

Selected tab: SupportedJDKVersions

Supported Browsers

 

The Cloudera Manager Admin Console, which you use to install, configure, manage, and monitor services, supports the following browsers:

  • Firefox 24 or 31
  • Google Chrome
  • Internet Explorer 9 or later
  • Safari 5 or later

 

 

Selected tab: SupportedBrowsers

Supported Databases

 

Cloudera Manager requires several databases. The Cloudera Manager Server stores information about configured services, role assignments, configuration history, commands, users, and running processes in a database of its own. You must also specify a database for the Activity Monitor and Reports Manager management services.

 

The database you choose to use must be configured to support UTF8 character set encoding. The embedded PostgreSQL database that is installed when you follow Installation Path A - Automated Installation by Cloudera Manager automatically provides UTF8 encoding. If you install a custom database, you may need to enable UTF8 encoding. The commands for enabling UTF8 encoding are described in each database's section under Cloudera Manager and Managed Service Databases.

 

After installing a database, upgrade to the latest patch version and apply any other appropriate updates. The available updates may be specific to the operating system on which it is installed.

 

Cloudera Manager and its supporting services can use the following databases:

  • MySQL - 5.0, 5.1, 5.5, and 5.6
  • Oracle 11gR2
  • PostgreSQL - 8.4, 9.1, and 9.2

 

For information about the databases supported by CDH, see CDH 4 Supported Databases and CDH 5 Supported Databases.

 

Selected tab: SupportedDatabases

Supported CDH and Managed Service Versions

 

The following versions of CDH and managed services are supported:

Warning: Cloudera Manager 5 does not support CDH 3 and you cannot upgrade Cloudera Manager 4 to Cloudera Manager 5 if you have a cluster running CDH 3. Therefore, to upgrade CDH 3 clusters to CDH 4 using Cloudera Manager you must use Cloudera Manager 4.

  • CDH 4 and CDH 5. The latest released versions of CDH 4 and CDH 5 are strongly recommended. For information on CDH 4 requirements, see CDH 4 Requirements and Supported Versions. For information on CDH 5 requirements, see CDH 5 Requirements and Supported Versions.
  • Cloudera Impala - Cloudera Impala is included with CDH 5. Cloudera Impala 1.2.1 with CDH 4.1.0 or later. For further information on Cloudera Impala requirements with CDH 4, see Cloudera Impala Requirements.
  • Cloudera Search - Cloudera Search is included with CDH 5. Cloudera Search 1.2.0 with CDH 4.6.0. For further information on Cloudera Search requirements with CDH 4, see Cloudera Search Requirements.
  • Apache Spark - 0.90 or later with CDH 4.4.0 or later.
  • Apache Accumulo - 1.4.3 with CDH 4.3.0, 1.4.4 with CDH 4.5.0, and 1.6.0 with CDH 4.6.0.

For more information, see the Cloudera Product Compatibility Matrix.

 

 

Selected tab: SupportedCDHandManagedServiceVersions

Resource Requirements

 

Cloudera Manager requires resources of the following types:

  • Disk Space
    • Cloudera Manager Server
      • 5 GB on the partition hosting /var.
      • 500 MB on the partition hosting /usr.
      • For parcels, the space required depends on the number of parcels you download to the Cloudera Manager Server and distribute to Agent hosts. You can download multiple parcels of the same product, of different versions and builds. If you are managing multiple clusters, there will be only one parcel of a given product/version/build/distribution downloaded on the Cloudera Manager Server—not one per cluster. In the local parcel repository on the Cloudera Manager Server the approximate sizes of the various parcels are as follows:
        • CDH 4.6 - ~700 MB per parcel, CDH 5 - ~1 GB per parcel
        • Impala - ~200 MB per parcel
        • Solr - ~ 400 MB per parcel
    • Cloudera Management Service - The Host Monitor and Service Monitor databases are stored on the partition hosting /var. Ensure that you have at least 20 GB available on this partition.For further information, see Data Storage for Monitoring Data.
    • Agents - On Agent hosts each unpacked parcel requires about three times the space of the downloaded parcel on the Cloudera Manager Server. By default unpacked parcels are located in /opt/cloudera/parcels.
  • RAM - 4 GB is appropriate for most cases, and is required when using Oracle databases. 2 GB may be sufficient for non-Oracle deployments involving fewer than 100 hosts. However, if you want to run the Cloudera Manager Server on a machine with 2 GB of RAM, you must tune down its maximum heap size (by modifying -Xmx in /etc/default/cloudera-scm-server). Otherwise the kernel may kill the Server for consuming too much RAM.
  • Python - Cloudera Manager uses Python. All supported operating systems contain a Python version 2.4 or higher. Cloudera Manager and CDH 4 require at least Python 2.4, but Hue in CDH 5 requires Python 2.6 or 2.7.

 

 

 

 

Selected tab: ResourceRequirements

 

Networking and Security Requirements

 

  • Cluster hosts must have a working network name resolution system and correctly formatted/etc/hosts file. All cluster hosts must have properly configured forward and reverse host resolution through DNS. The /etc/hosts files must contain consistent information about host names and addresses across all hosts. A properly formatted /etc/hosts should be similar to the following example:

    127.0.0.1 localhost.localdomain localhost
    192.168.1.1 cluster-01.example.com cluster-01
    192.168.1.2 cluster-02.example.com cluster-02
    192.168.1.3 cluster-03.example.com cluster-03

    The /etc/hosts file must not have duplicate IP addresses.
  • In most cases, the Cloudera Manager Server must have SSH access to the cluster hosts when you run the installation or upgrade wizard. You must log in using a root account or an account that has password-less sudo permission. For authentication during the installation and upgrade procedures, you must either enter the password or upload a public and private key pair for the root or sudo user account. If you want to use a public and private key pair, the public key must be installed on the cluster hosts before you use Cloudera Manager.

    Cloudera Manager uses SSH only during the initial install or upgrade. Once your cluster is set up, you can disable root SSH access or change the root password. Cloudera Manager does not save SSH credentials and all credential information is discarded once the installation is complete. For further information, see Permission Requirements.

  • The Cloudera Manager Agent runs as root so that it can make sure the required directories are created and that processes and files are owned by the appropriate user (for example, the hdfs andmapred users).
  • No blocking by Security-Enhanced Linux (SELinux).
  • Disable Ipv6 on all hosts.
  • No blocking by iptables or firewalls; make sure port 7180 is open because it is the port used to access Cloudera Manager after installation. Cloudera Manager communicates using specific ports, which must be open. See Configuring Ports for Cloudera Manager.
  • For RedHat and CentOS, make sure the/etc/sysconfig/network file on each system contains the hostname you have just set (or verified) for that system.
  • Cloudera Manager and CDH use several user accounts and groups to complete their tasks. The set of user accounts and groups varies according to which components you choose to install. Do not delete these accounts or groups and do not modify their permissions and rights. Ensure no existing systems obstruct the functioning of these accounts and groups. For example, if you have scripts that delete user accounts not in a white-list, add these accounts to the list of permitted accounts. Cloudera Manager, CDH, and managed services create and use the following accounts and groups:

    Account Type Product

    cloudera-scm

    User and group Cloudera Manager

    flume

    User and group CDH 4, CDH 5

    hadoop

    Group CDH 4, CDH 5

    hbase

    User and group CDH 4, CDH 5

    hdfs

    User and group. Must also be a member of the hadoop group. CDH 4, CDH 5

    hive

    User and group CDH 4, CDH 5

    httpfs

    User and group CDH 4, CDH 5

    hue

    User and group CDH 4, CDH 5

    impala

    User and group. Must also be member of the hdfs and hivegroups. CDH 4.1 or later, CDH 5

    llama

    User and group CDH 5

    mapred

    User and group. Must also be a member of the hadoop group. CDH 4, CDH 5

    oozie

    User and group CDH 4, CDH 5

    solr

    User and group CDH 4.3 and later, CDH 5

    spark

    User and group Spark, CDH 5

    sqoop

    User and group CDH 4, CDH 5

    sqoop2

    User. Must be member of the sqoopgroup. CDH 4.2 and later, CDH 5

    yarn

    User and group CDH 4, CDH 5

    zookeeper

    User and group CDH 4, CDH 5

 

Selected tab: NetworkingandSecurityRequirements
Selected tab: SystemRequirements

What's New in Cloudera Manager 5.1.0

  • SSL Encryption:
    • Supports several new SSL-related configuration parameters for HDFS, MapReduce, YARN and HBase, which allow you to configure and enable encrypted shuffle and encrypted web UIs for these services. See Configuring SSL Encryption in Cloudera Manager.
    • Cloudera Manager now also supports the monitoring of HDFS, MapReduce, YARN, and HBase when SSL is enabled for these services. New configuration parameters allow you to specify the location and password of the truststore used to verify certificates in HTTPS communication with CDH services and the Cloudera Manager Server.
  • Sentry Service:
    • A new Sentry service that stores the authorization metadata in an underlying relational database and allows you to use Grant/Revoke statements to modify privileges. See The Sentry Service.
    • You can also configure the Sentry service to allow Pig, MapReduce, and WebHCat queries access to Sentry-secured data stored in Hive. SeeConfiguring Pig and HCatalog for the Sentry Service.
  • Kerberos Authentication:
    • Now supports a Kerberos cluster using an Active Directory KDC.
    • New wizard to enable Kerberos on an existing cluster. The wizard works with both MIT KDC and Active Directory KDC.
    • Ability to configure and deploy Kerberos client configuration (krb5.conf) on a cluster.
  • Spark Service - added the History Server role
  • Impala - added support for Llama ApplicationMaster High Availability
  • User Roles - there are two new roles: Operator and Configurator that support fine-grained access to Cloudera Manager features. See Cloudera Manager User Accounts.
  • Monitoring
    • Updates to Oozie monitoring
    • New Hive Metastore Canary
  • UI - The UI has been updated to improve scalability. The Home page Status tab can be configured to display clusters in a full or summary format. There is a new Cluster page for each cluster. The Hosts and Instances pages have added faceted filters.

Selected tab: WhatsNew

Cloudera Enterprise Extensions

ODBC and JDBC Drivers

The Cloudera ODBC and JDBC Drivers for Hive and Impala enable your enterprise users to access Hadoop data through Business Intelligence (BI) applications with ODBC/JDBC support.

Data Transfer Connectors

Sqoop Connectors are used to transfer data between Apache Hadoop systems and external databases or Enterprise Data Warehouses. These connectors allow Hadoop and platforms like CDH to complement existing architecture with seamless data transfer.

Want to Get Involved or Learn More?

Check out our other resources

Cloudera Community

Collaborate with your peers, industry experts, and Clouderans to make the most of your investment in Hadoop.

Cloudera University

Receive expert Hadoop training through Cloudera University, the industry's only truly dynamic Hadoop training curriculum that’s updated regularly to reflect the state of the art in big data.