Cloudera Manager 4.8.3

A Single Interface to Manage Your CDH Cluster

Cloudera Manager 4.x works with both CDH 3.x* and CDH 4.x. and is available with:
Cloudera Express - Easily deploy, manage, monitor and perform diagnostics on your Hadoop cluster
Cloudera Enterprise – Includes all the above capabilities, plus advanced management features and support including zero downtime upgrades and backup and disaster recovery.

*Please note: CDH 3 is no longer maintained. CM 4.x will continue to support CDH 3 but it is strongly recommended that you upgrade to CDH 4.

Instructions for Installing Previous Cloudera Manager Versions

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

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

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

Known Issues Fixed in Cloudera Manager 4.8.3

Sensitive configuration values exposed in Cloudera Manager

Certain configuration values that are stored in Cloudera Manager are considered sensitive, such as database passwords. These configuration values should be inaccessible to non-administrator users, and this is enforced in the Cloudera Manager Administration Console. However, these configuration values are not redacted when they are read through the API, possibly making them accessible to users who should not have such access.

Gateway role configurations not respected when deploying client configurations

Gateway configurations set for gateway role groups other than the default one or at the role level were not being respected.

Insufficient password hashing in Cloudera Manager

In versions of Cloudera Manager earlier than 4.8.3, user passwords are only hashed once. Passwords should be hashed multiple times to increase the cost of dictionary based attacks, where an attacker tries many candidate passwords to find a match. The issue only affects user accounts that are stored in the Cloudera Manager database. User accounts that are managed externally (for example, with LDAP or Active Directory) are not affected.

In addition, because of this issue, Cloudera Manager 4.8.3 cannot be upgraded to Cloudera Manager 5.0.0. Cloudera Manager 4.8.3 must be upgraded to 5.0.1 or later.

Workaround: None. Upgrade to Cloudera Manager 4.8.3 or 5.0.1.

Some Impala queries do not appear on the Cloudera Manager Impala Queries page

Many Impala queries run on Impala version 1.3.1 will not show on the Cloudera Manager Impala Queries Page.

Workaround: None. Upgrade to Cloudera Manager 4.8.3.

Gateway role configs not respected when deploying client configs

Gateway role configurations are not respected when deploying client configurations.

Workaround: None. Upgrade to Cloudera Manager 4.8.3

Error if attempting to watch more than 1024 directories in Reports Manager

Reports Manager does not allow more than 1024 directories to be watched when configuring directory-based usage reports.

Workaround: None. Upgrade to Cloudera Manager 4.8.3.

Log messages beginning with a newline character cause log searching to fail

In previous releases of Cloudera Manager, log messages beginning with a newline character would cause log searching to fail, and increase CPU utilization for the Cloudera Manager Agent.

Workaround: None. Upgrade to Cloudera Manager 4.8.3.

Filtering on host does not return a result even if the job shows the host

In the Cloudera Manager UI, clicking Activities > MapReduce Jobs, selecting a MapReduce job, and filtering on "host" does not return a result even if the job shows the host.

Workaround: None. Upgrade to Cloudera Manager 4.8.3.

Cluster Installation automatically aborts with Google Chrome and Cloudera Manager 4.8.2

Cluster Installation automatically aborts with Google Chrome and Cloudera Manager 4.8.2.

Workaround: None. Upgrade to Cloudera Manager 4.8.3.

Documentation reflects requirement to enable at least Level 1 encryption before enabling Kerberos authentication

The Cloudera Manager manual Configuring Hadoop Security with Cloudera Manager now indicates that before enabling Kerberos authentication you should first enable at least Level 1 encryption.

Cloudera Manager 4.8.3 System Requirements:

Supported Operating Systems

  • Red Hat-compatible
    • Red Hat Enterprise Linux 5.7 and CentOS 5.7, 64-bit
    • Red Hat Enterprise Linux 6.2 and 6.4, and CentOS 6.2 and 6.4, 64-bit
    • Oracle Enterprise Linux 5.6 and 6.4 with Unbreakable Enterprise Kernel, 64-bit
  • SLES
    • SUSE Linux Enterprise Server 11, 64-bit. Service Pack 1 or later is required. Also, the SUSE Linux Enterprise Software Development Kit 11 SP1 is required on cluster hosts running the Cloudera Manager Agents (not required on the Cloudera Manager Server host); you can download the SDK here.
  • Debian
    • Debian 6.0 (Squeeze), 64-bit
  • Ubuntu
    • Ubuntu 10.04 (Lucid Lynx), 64-bit
    • Ubuntu 12.04 (Precise Pangolin), 64-bit
  Note: For Hadoop to work properly, using the same version of the same operating system on all cluster hosts is strongly recommended.

Supported JDK Versions

The Cloudera Manager Installation program installs Oracle JDK 1.6 (1.6.0_31) if a JDK is not already installed. However, Cloudera Manager 4.5.1 and later also support JDK 1.7.

Supported Browsers

The Cloudera Manager Admin Console, which you use to configure, manage, and monitor CDH, supports the following browsers:
  • Firefox 11 or later
  • Google Chrome
  • Internet Explorer 9
  • Safari 5 or later

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. The Activity Monitor, Service Monitor, Report Manager, and Host Monitor also each use a database to store information.

The database you choose to use must be configured to support UTF8 character set encoding. The embedded PostgreSQL database that is installed using Path A 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 Installing and Configuring Databases.

After installing a database, upgrade to the latest patch version and apply any other appropriate updates. Note that 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 database systems and releases:
  • MySQL - 5.0, 5.1, 5.5
  • Oracle - 10g Release 2, 11g Release 2
  • PostgreSQL - 8.1, 8.3, 8.4, 9.1

Supported Supported CDH and Other Managed Service Versions

  • CDH3 Update 1 (cdh3u1) or later (for Oozie support, CDH3 Update 2 or later is required) and CDH4.
      Important: Cloudera Manager version 3.x and CDH3 have reached End of Maintenance (EOM) as of June 20, 2013. Cloudera will not support or provide patches for any of the Cloudera Manager version 3.x and CDH3 releases. Even though Cloudera Manager 4.x will continue to support CDH3, it is strongly recommended that you upgrade to CDH4. See Upgrading existing installations of CDH3 to CDH4 for more details.
      Important: The latest released versions of CDH4 are strongly recommended.
    For information on CDH 4 requirements, see CDH 4 Requirements and Supported Versions.
  • Impala 1.2.1 or later with CDH4.1 or later. For information on Cloudera Impala requirements, see Cloudera Impala Requirements.
  • Cloudera Search 1.2.0 with CDH4.6.0. For information on Cloudera Search requirements, see Cloudera Search Requirements.
      Note: Cloudera Manager allows you to add Solr and Key-Value Store Indexer services even if the CDH version deployed in your cluster (for example, CDH 4.4) does not support Cloudera Search. However, you will not be able to start the services.
  • Apache Spark 0.9 with CDH4.4.0 or later, with CDH installed using parcels. If you installed CDH using packages, you must reinstall or upgrade it using parcels.

Resource Requirements

  • Disk Space
    • Cloudera Manager Server:
      • 5 GB on the partition hosting /var.
      • 500 MB on the partition hosting /usr.
      • For parcels, the space required will depend on the number of parcels you download to the Cloudera Manager server, and distribute to agent nodes. You can download multiple parcels of the same product, of different versions and builds.

        Even if you are managing multiple clusters, there will be only one parcel of any given product/version/build/distro downloaded on the Cloudera Manager server — not one per cluster.

        In the local parcel repo on the Cloudera Manager server the approximate sizes of the various parcels (as of Cloudera Manager 4.6) are as follows:

        • CDH4.3 — slightly over 700MB per parcel.
        • Impala — approximately 200MB per parcel.
        • Cloudera Search (Solr) — approximately 400MB per parcel.
    • Cloudera Manager Agent Each unpacked parcel will require about three times the space of the downloaded parcel on the Cloudera Manager Server.
  • RAM - 4 GB is appropriate for most cases, and is required when using Oracle databases. 2GB may be sufficient for non-Oracle deployments involving fewer than 100 hosts.
  • Python - Cloudera Manager uses Python. Python is part of the default installation for all operating systems that Cloudera Manager supports, so there is no need to complete any installation tasks to make Python available. Cloudera Manager is tested with the default installation. Modifying the Python installation available on systems on which you install Cloudera Manager is not supported.

Networking and Security Requirements

  • Cluster hosts must have a working network name resolution system. Properly configuring DNS and reverse DNS meets this requirement. If you use /etc/hosts instead of DNS, all hosts files must contain consistent information about host names and addresses across all nodes. For example, /etc/hosts might contain something of the form:	localhost.localdomain	localhost	cluster-01	cluster-02	cluster-03 
  • In most cases, the Cloudera Manager Server must have SSH access to the cluster hosts when you run the installation or upgrade wizard. This does not apply if you install Cloudera Manager using Installation Path B - Installation Using Your Own Method . For further information, see Permission Requirements.
      Note: 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 will need to 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. Authentication is not supported for accounts that have password-protected sudo permission. Cloudera Manager uses SSH only during the initial install or upgrade. Once your cluster is set up, you can safely 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.
  • 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 user and mapred user).
  • No blocking by Security-Enhanced Linux (SELinux).
  • Disable Ipv6 on all machines.
  • 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. For additional information, see Configuring Ports for Cloudera Manager.
  • For RedHat/CentOS operating systems, make sure the/etc/sysconfig/network file on each system contains the hostname you have just set (or verified) for that system. (This does not apply to Debian/Ubuntu or SLES).
  • Cloudera Manager, CDH, and managed services 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 and CDH create and use the following accounts and groups:
    Account Type Product
    User and group Cloudera Manager
    User and group CDH3 and CDH4
    Group CDH3 and CDH4
    User and group CDH3 and CDH4
    User and group. Must also be a member of the hadoop group. CDH3 and CDH4
    User and group CDH3 and CDH4
    User and group CDH4
    User and group CDH3 and CDH4
    User and group CDH4.1
    User and group. Must also be a member of the hadoop group. CDH3 and CDH4
    User and group CDH3 and CDH4
    User and group CDH4.3 and later
    User and group Spark
    User and group CDH3 and CDH4
    User. Must be a member of the sqoop group. CDH4.2 and later
    User and group CDH4
    User and group CDH3 and CDH4

For additional port information, see Configuring Ports for Cloudera Manager.