This is the documentation for Cloudera 5.4.x. Documentation for other versions is available at Cloudera Documentation.

Installation Path B - Manual Installation Using Cloudera Manager Packages

Before proceeding with this path for a new installation, review Cloudera Manager Deployment. If you are upgrading a Cloudera Manager existing installation, see Upgrading Cloudera Manager.

To install the Cloudera Manager Server using packages, follow the instructions in this section. You can also use Puppet or Chef to install the packages. The general steps in the procedure for Installation Path B follow.

  1. Before You Begin
    1. Perform Configuration Required by Single User Mode
    2. (CDH 5 only) On RHEL 5 and CentOS 5, Install Python 2.6 or 2.7
    3. Install and Configure Databases
  2. Establish Your Cloudera Manager Repository Strategy
    1. Red Hat-compatible
    2. SLES
    3. Ubuntu or Debian
  3. Install the Oracle JDK
    1. Install the Cloudera Manager Server Packages
    2. Set up a Database for the Cloudera Manager Server
    3. (Optional) Manually Install the Oracle JDK, Cloudera Manager Agent, and CDH and Managed Service Packages
      1. Install the Oracle JDK
      2. Install Cloudera Manager Agent Packages
      3. Install CDH and Managed Service Packages
      4. (Optional) Install Key Trustee KMS
    4. Start the Cloudera Manager Server
    5. (Optional) Start the Cloudera Manager Agents
    6. Start and Log into the Cloudera Manager Admin Console
      1. Choose Cloudera Manager Edition and Hosts
      2. Choose the Software Installation Type and Install Software
      3. Add Services
        1. Change the Default Administrator Password
        2. Configure Oozie Data Purge Settings
        3. Test the Installation

        During Cloudera Manager installation you can choose to install CDH and managed service as parcels or packages. For packages, you can choose to have Cloudera Manager install the packages or install them yourself.

        Before You Begin

        Perform Configuration Required by Single User Mode

        If you are creating a Cloudera Manager deployment that employs single user mode, perform the configuration steps described in Single User Mode Requirements.

        (CDH 5 only) On RHEL 5 and CentOS 5, Install Python 2.6 or 2.7

        CDH 5 Hue will only work with the default system Python version of the operating system it is being installed on. For example, on RHEL/CentOS 6 you will need Python 2.6 to start Hue.
        To install packages from the EPEL repository, download the appropriate repository rpm packages to your machine and then install Python using yum. For example, use the following commands for RHEL 5 or CentOS 5:
        $ su -c 'rpm -Uvh http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm'
        ...
        $ yum install python26

        Install and Configure Databases

        Read Cloudera Manager and Managed Service Data Stores. If you are using an external database, install and configure a database as described in MySQL Database, Oracle Database, or External PostgreSQL Database.

        Establish Your Cloudera Manager Repository Strategy

        Cloudera recommends installing products using package management tools such as yum for Red Hat compatible systems, zypper for SLES, and apt-get for Debian/Ubuntu. These tools depend on access to repositories to install software. For example, Cloudera maintains Internet-accessible repositories for CDH and Cloudera Manager installation files. Strategies for installing Cloudera Manager include:

        • Standard Cloudera repositories. For this method, ensure you have added the required repository information to your systems. For Cloudera Manager repository locations and client repository files, see Cloudera Manager Version and Download Information.
        • Internally hosted repositories. You might use internal repositories for environments where hosts do not have access to the Internet. For information about preparing your environment, see Understanding Custom Installation Solutions. When using an internal repository, you must copy the repo or list file to the Cloudera Manager Server host and update the repository properties to point to internal repository URLs.

        Red Hat-compatible

        1. Save the appropriate Cloudera Manager repo file (cloudera-manager.repo) for your system:
        2. Copy the repo file to the /etc/yum.repos.d/ directory.

        SLES

        1. Run the following command:
          $ sudo zypper addrepo -f http://archive.cloudera.com/cm5/sles/11/x86_64/cm/cloudera-manager.repo
        2. Update your system package index by running:
          $ sudo zypper refresh

        Ubuntu or Debian

        1. Save the appropriate Cloudera Manager list file (cloudera.list) for your system:
        2. Copy the content of that file to the cloudera-manager.list file in the /etc/apt/sources.list.d/ directory.
        3. Update your system package index by running:
          $ sudo apt-get update

        Install the Oracle JDK

        Install the Oracle Java Development Kit (JDK) on the Cloudera Manager Server host.

        The JDK is included in the Cloudera Manager 5 repositories. After downloading and editing the repo or list file, install the JDK as follows:
        OS Command
        RHEL
        $ sudo yum install oracle-j2sdk1.7
        SLES
        $ sudo zypper install oracle-j2sdk1.7
        Ubuntu or Debian
        $ sudo apt-get install oracle-j2sdk1.7

        Install the Cloudera Manager Server Packages

        Install the Cloudera Manager Server packages either on the host where the database is installed, or on a host that has access to the database. This host need not be a host in the cluster that you want to manage with Cloudera Manager. On the Cloudera Manager Server host, type the following commands to install the Cloudera Manager packages.
        OS Command
        RHEL, if you have a yum repo configured
        $ sudo yum install cloudera-manager-daemons cloudera-manager-server
        RHEL,if you're manually transferring RPMs
        $ sudo yum --nogpgcheck localinstall cloudera-manager-daemons-*.rpm
        $ sudo yum --nogpgcheck localinstall cloudera-manager-server-*.rpm
        SLES
        $ sudo zypper install cloudera-manager-daemons cloudera-manager-server 
        Ubuntu or Debian
        $ sudo apt-get install cloudera-manager-daemons cloudera-manager-server 

        Set up a Database for the Cloudera Manager Server

        Depending on whether you are using an external database, or the embedded PostgreSQL database, do one of the following:

        (Optional) Manually Install the Oracle JDK, Cloudera Manager Agent, and CDH and Managed Service Packages

        You can use Cloudera Manager to install the Oracle JDK, Cloudera Manager Agent packages, CDH, and managed service packages in Choose the Software Installation Type and Install Software, or you can install them manually. To use Cloudera Manager to install the packages, you must meet the requirements described in Cloudera Manager Deployment.

          Important: If you are installing CDH and managed service software using packages and you want to manually install Cloudera Manager Agent or CDH packages, you must manually install them both following the procedures in this section; you cannot choose to install only one of them this way.

        If you are going to use Cloudera Manager to install software, skip this section and go to Start the Cloudera Manager Server. Otherwise, to manually install software, proceed with the steps in this section.

        Install the Oracle JDK

        Install the Oracle JDK on the cluster hosts. Cloudera Manager 5 can manage both CDH 5 and CDH 4, and the required JDK version varies accordingly:

        Install Cloudera Manager Agent Packages

        To install the Cloudera Manager Agent packages manually, do the following on every Cloudera Manager Agent host (including those that will run one or more of the Cloudera Management Service roles: Service Monitor, Activity Monitor, Event Server, Alert Publisher, or Reports Manager):
        1. Use one of the following commands to install the Cloudera Manager Agent packages:
          OS Command
          RHEL, if you have a yum repo configured:
          $ sudo yum install cloudera-manager-agent cloudera-manager-daemons
          RHEL, if you're manually transferring RPMs:
          $ sudo yum --nogpgcheck localinstall cloudera-manager-agent-package.*.x86_64.rpm cloudera-manager-daemons
          SLES
          $ sudo zypper install cloudera-manager-agent cloudera-manager-daemons
          Ubuntu or Debian
          $ sudo apt-get install cloudera-manager-agent cloudera-manager-daemons
        2. On every Cloudera Manager Agent host, configure the Cloudera Manager Agent to point to the Cloudera Manager Server by setting the following properties in the /etc/cloudera-scm-agent/config.ini configuration file:
          Property Description
          server_host Name of the host where Cloudera Manager Server is running.
          server_port Port on the host where Cloudera Manager Server is running.
          For more information on Agent configuration options, see Agent Configuration File.

        Install CDH and Managed Service Packages

        1. Choose a repository strategy:
          • Standard Cloudera repositories. For this method, ensure you have added the required repository information to your systems.
          • Internally hosted repositories. You might use internal repositories for environments where hosts do not have access to the Internet. For information about preparing your environment, see Understanding Custom Installation Solutions. When using an internal repository, you must copy the repo or list file to the Cloudera Manager Server host and update the repository properties to point to internal repository URLs.
        2. Install packages:
          CDH Version Procedure
          CDH 5
          • Red Hat
            1. Download and install the "1-click Install" package.
              1. Download the CDH 5 "1-click Install" package.

                Click the entry in the table below that matches your Red Hat or CentOS system, choose Save File, and save the file to a directory to which you have write access (for example, your home directory).

                OS Version Click this Link
                Red Hat/CentOS/Oracle 5 Red Hat/CentOS/Oracle 5 link
                Red Hat/CentOS/Oracle 6 Red Hat/CentOS/Oracle 6 link
              2. Install the RPM:
                • Red Hat/CentOS/Oracle 5
                  $ sudo yum --nogpgcheck localinstall cloudera-cdh-5-0.x86_64.rpm 
                • Red Hat/CentOS/Oracle 6
                  $ sudo yum --nogpgcheck localinstall cloudera-cdh-5-0.x86_64.rpm
            2. (Optionally) add a repository key:
              • Red Hat/CentOS/Oracle 5
                $ sudo rpm --import http://archive.cloudera.com/cdh5/redhat/5/x86_64/cdh/RPM-GPG-KEY-cloudera
              • Red Hat/CentOS/Oracle 6
                $ sudo rpm --import http://archive.cloudera.com/cdh5/redhat/6/x86_64/cdh/RPM-GPG-KEY-cloudera
            3. Install the CDH packages:
              $ sudo yum clean all
              $ sudo yum install avro-tools crunch flume-ng hadoop-hdfs-fuse hadoop-hdfs-nfs3 hadoop-httpfs hadoop-kms hbase-solr hive-hbase hive-webhcat hue-beeswax hue-hbase hue-impala hue-pig hue-plugins hue-rdbms hue-search hue-spark hue-sqoop hue-zookeeper impala impala-shell kite llama mahout oozie pig pig-udf-datafu search sentry solr-mapreduce spark-core spark-master spark-worker spark-history-server spark-python sqoop sqoop2 whirr
                Note: Installing these packages also installs all the other CDH packages required for a full CDH 5 installation.
          • SLES
            1. Download and install the "1-click Install" package.
              1. Download the CDH 5 "1-click Install" package.

                Click this link, choose Save File, and save it to a directory to which you have write access (for example, your home directory).

              2. Install the RPM:
                $ sudo rpm -i cloudera-cdh-5-0.x86_64.rpm
              3. Update your system package index by running:
                $ sudo zypper refresh
            2. (Optionally) add a repository key:
              $ sudo rpm --import http://archive.cloudera.com/cdh5/sles/11/x86_64/cdh/RPM-GPG-KEY-cloudera
            3. Install the CDH packages:
              $ sudo zypper clean --all
              $ sudo zypper install avro-tools crunch flume-ng hadoop-hdfs-fuse hadoop-hdfs-nfs3 hadoop-httpfs hadoop-kms hbase-solr hive-hbase hive-webhcat hue-beeswax hue-hbase hue-impala hue-pig hue-plugins hue-rdbms hue-search hue-spark hue-sqoop hue-zookeeper impala impala-shell kite llama mahout oozie pig pig-udf-datafu search sentry solr-mapreduce spark-core spark-master spark-worker spark-history-server spark-python sqoop sqoop2 whirr
                Note: Installing these packages also installs all the other CDH packages required for a full CDH 5 installation.
          • Ubuntu and Debian
            1. Download and install the "1-click Install" package
              1. Download the CDH 5 "1-click Install" package:
                OS Version Click this Link
                Wheezy Wheezy link
                Precise Precise link
                Trusty Trusty link
              2. Install the package by doing one of the following:
                • Choose Open with in the download window to use the package manager.
                • Choose Save File, save the package to a directory to which you have write access (for example, your home directory), and install it from the command line. For example:
                  sudo dpkg -i cdh5-repository_1.0_all.deb
            2. Optionally add a repository key:
              • Debian Wheezy
                $ curl -s http://archive.cloudera.com/cdh5/debian/wheezy/amd64/cdh/archive.key | sudo apt-key add -
              • Ubuntu Precise
                $ curl -s http://archive.cloudera.com/cdh5/ubuntu/precise/amd64/cdh/archive.key | sudo apt-key add -
            3. Install the CDH packages:
              $ sudo apt-get update
              $ sudo apt-get install avro-tools crunch flume-ng hadoop-hdfs-fuse hadoop-hdfs-nfs3 hadoop-httpfs hadoop-kms hbase-solr hive-hbase hive-webhcat hue-beeswax hue-hbase hue-impala hue-pig hue-plugins hue-rdbms hue-search hue-spark hue-sqoop hue-zookeeper impala impala-shell kite llama mahout oozie pig pig-udf-datafu search sentry solr-mapreduce spark-core spark-master spark-worker spark-history-server spark-python sqoop sqoop2 whirr
                Note: Installing these packages also installs all the other CDH packages required for a full CDH 5 installation.
          CDH 4, Impala, and Solr
          • Red Hat-compatible
            1. Click the entry in the table at CDH Download Information that matches your Red Hat or CentOS system.
            2. Navigate to the repo file (cloudera-cdh4.repo) for your system and save it in the /etc/yum.repos.d/ directory.
            3. Optionally add a repository key:
              • Red Hat/CentOS/Oracle 5
                $ sudo rpm --import http://archive.cloudera.com/cdh4/redhat/5/x86_64/cdh/RPM-GPG-KEY-cloudera
              • Red Hat/CentOS 6
                $ sudo rpm --import http://archive.cloudera.com/cdh4/redhat/6/x86_64/cdh/RPM-GPG-KEY-cloudera
            4. Install packages on every host in your cluster:
              1. Install CDH 4 packages:
                $ sudo yum -y install bigtop-utils bigtop-jsvc bigtop-tomcat hadoop hadoop-hdfs hadoop-httpfs hadoop-mapreduce hadoop-yarn hadoop-client hadoop-0.20-mapreduce hue-plugins hbase hive oozie oozie-client pig zookeeper
              2. To install the hue-common package and all Hue applications on the Hue host, install the hue meta-package:
                $ sudo yum install hue 
            5. (Requires CDH 4.2 or later) Install Impala
              1. In the table at Cloudera Impala Version and Download Information, click the entry that matches your Red Hat or CentOS system.
              2. Navigate to the repo file for your system and save it in the /etc/yum.repos.d/ directory.
              3. Install Impala and the Impala Shell on Impala machines:
                $ sudo yum -y install impala impala-shell
            6. (Requires CDH 4.3 or later) Install Search
              1. In the table at Cloudera Search Version and Download Information, click the entry that matches your Red Hat or CentOS system.
              2. Navigate to the repo file for your system and save it in the /etc/yum.repos.d/ directory.
              3. Install the Solr Server on machines where you want Cloudera Search.
                $ sudo yum -y install solr-server
          • SLES
            1. Run the following command:
              $ sudo zypper addrepo -f http://archive.cloudera.com/cdh4/sles/11/x86_64/cdh/cloudera-cdh4.repo
            2. Update your system package index by running:
              $ sudo zypper refresh
            3. Optionally add a repository key:
              $ sudo rpm --import http://archive.cloudera.com/cdh4/sles/11/x86_64/cdh/RPM-GPG-KEY-cloudera  
            4. Install packages on every host in your cluster:
              1. Install CDH 4 packages:
                $ sudo zypper install bigtop-utils bigtop-jsvc bigtop-tomcat hadoop hadoop-hdfs hadoop-httpfs hadoop-mapreduce hadoop-yarn hadoop-client hadoop-0.20-mapreduce hue-plugins hbase hive oozie oozie-client pig zookeeper
              2. To install the hue-common package and all Hue applications on the Hue host, install the hue meta-package:
                $ sudo zypper install hue 
              3. (Requires CDH 4.2 or later) Install Impala
                1. Run the following command:
                  $ sudo zypper addrepo -f http://archive.cloudera.com/impala/sles/11/x86_64/impala/cloudera-impala.repo
                2. Install Impala and the Impala Shell on Impala machines:
                  $ sudo zypper install impala impala-shell
              4. (Requires CDH 4.3 or later) Install Search
                1. Run the following command:
                  $ sudo zypper addrepo -f http://archive.cloudera.com/search/sles/11/x86_64/search/cloudera-search.repo
                2. Install the Solr Server on machines where you want Cloudera Search.
                  $ sudo zypper install solr-server
          • Ubuntu or Debian
            1. In the table at CDH Version and Packaging Information, click the entry that matches your Ubuntu or Debian system.
            2. Navigate to the list file (cloudera.list) for your system and save it in the /etc/apt/sources.list.d/ directory. For example, to install CDH 4 for 64-bit Ubuntu Lucid, your cloudera.list file should look like:
              deb [arch=amd64] http://archive.cloudera.com/cdh4/ubuntu/lucid/amd64/cdh lucid-cdh4 contrib
              deb-src http://archive.cloudera.com/cdh4/ubuntu/lucid/amd64/cdh lucid-cdh4 contrib
            3. Optionally add a repository key:
              • Ubuntu Lucid
                $ curl -s http://archive.cloudera.com/cdh4/ubuntu/lucid/amd64/cdh/archive.key | sudo apt-key add -
              • Ubuntu Precise
                $ curl -s http://archive.cloudera.com/cdh4/ubuntu/precise/amd64/cdh/archive.key | sudo apt-key add -
              • Debian Squeeze
                $ curl -s http://archive.cloudera.com/cdh4/debian/squeeze/amd64/cdh/archive.key | sudo apt-key add -
            4. Install packages on every host in your cluster:
              1. Install CDH 4 packages:
                $ sudo apt-get install bigtop-utils bigtop-jsvc bigtop-tomcat hadoop hadoop-hdfs hadoop-httpfs hadoop-mapreduce hadoop-yarn hadoop-client hadoop-0.20-mapreduce hue-plugins hbase hive oozie oozie-client pig zookeeper
              2. To install the hue-common package and all Hue applications on the Hue host, install the hue meta-package:
                $ sudo apt-get install hue 
              3. (Requires CDH 4.2 or later) Install Impala
                1. In the table at Cloudera Impala Version and Download Information, click the entry that matches your Ubuntu or Debian system.
                2. Navigate to the list file for your system and save it in the /etc/apt/sources.list.d/ directory.
                3. Install Impala and the Impala Shell on Impala machines:
                  $ sudo apt-get install impala impala-shell
              4. (Requires CDH 4.3 or later) Install Search
                1. In the table at Cloudera Search Version and Download Information, click the entry that matches your Ubuntu or Debian system.
                2. Install Solr Server on machines where you want Cloudera Search:
                  $ sudo apt-get install solr-server

        (Optional) Install Key Trustee KMS

        If you want to use Cloudera Navigator Key Trustee Server as the underlying key store for HDFS Data At Rest Encryption, install the Key Trustee KMS.

          Important: Following these instructions will install the required software to add the Key Trustee KMS service to your cluster; this enables you to use an existing Cloudera Navigator Key Trustee Server as the underlying keystore for HDFS Data At Rest Encryption. This does not install Cloudera Navigator Key Trustee Server. Contact Cloudera Support for Key Trustee Server documentation or assistance deploying Key Trustee Server.
        To install the Key Trustee KMS:
        1. Identify the appropriate repository for your operating system, and copy the repository URL:
          OS Version Repository URL
          RHEL-compatible 6 RHEL 6 Repository
          RHEL-compatible 5 RHEL 5 Repository
          SLES 11 SLES 11 Repository
          Ubuntu Trusty (14.04) Ubuntu Trusty Repository
          Ubuntu Precise (12.04) Ubuntu Precise Repository
          Debian Wheezy (7.0 and 7.1) Debian Wheezy Repository
        2. Add the repository to your system, using the appropriate procedure for your operating system:
          • RHEL-compatible

            Download the repository and copy it to the /etc/yum.repos.d/ directory. Refresh the package index by running sudo yum clean all.

          • SLES
            Add the repository to your system using the following command:
            $ sudo zypper addrepo -f repository_url

            Refresh the package index by running sudo zypper refresh.

          • Ubuntu or Debian

            Copy the content of the appropriate cloudera.list file from the above repository table and append it to the /etc/apt/sources.list.d/cloudera.list file. Create the file if it does not exist. Refresh the package index by running sudo apt-get update.

        3. Install the keytrustee-keyprovider package, using the appropriate command for your operating system:
          • RHEL-compatible
            $ sudo yum install keytrustee-keyprovider
          • SLES
            $ sudo zypper install keytrustee-keyprovider
          • Ubuntu or Debian
            $ sudo apt-get install keytrustee-keyprovider

        Start the Cloudera Manager Server

          Important: When you start the Cloudera Manager Server and Agents, Cloudera Manager assumes you are not already running HDFS and MapReduce. If these services are running:
        1. Shut down HDFS and MapReduce. See Stopping Services (CDH 4) or Stopping CDH Services Using the Command Line (CDH 5) for the commands to stop these services.
        2. Configure the init scripts to not start on boot. Use commands similar to those shown in Configuring init to Start Core Hadoop System Services (CDH 4) or Configuring init to Start Hadoop System Services (CDH 5), but disable the start on boot (for example, $ sudo chkconfig hadoop-hdfs-namenode off).
        Contact Cloudera Support for help converting your existing Hadoop configurations for use with Cloudera Manager.
        1. Run this command on the Cloudera Manager Server host:
          $ sudo service cloudera-scm-server start
          If the Cloudera Manager Server does not start, see Troubleshooting Installation and Upgrade Problems.

        (Optional) Start the Cloudera Manager Agents

        If you are going to use Cloudera Manager to install Cloudera Manager Agent packages, skip this section and go to Start and Log into the Cloudera Manager Admin Console. Otherwise, run this command on each Agent host:
        $ sudo service cloudera-scm-agent start
        When the Agent starts, it contacts the Cloudera Manager Server. If communication fails between a Cloudera Manager Agent and Cloudera Manager Server, see Troubleshooting Installation and Upgrade Problems.

        When the Agent hosts reboot, cloudera-scm-agent starts automatically.

        Start and Log into the Cloudera Manager Admin Console

        The Cloudera Manager Server URL takes the following form http://Server host:port, where Server host is the fully qualified domain name or IP address of the host where the Cloudera Manager Server is installed, and port is the port configured for the Cloudera Manager Server. The default port is 7180.
        1. Wait several minutes for the Cloudera Manager Server to complete its startup. To observe the startup process, run tail -f /var/log/cloudera-scm-server/cloudera-scm-server.log on the Cloudera Manager Server host. If the Cloudera Manager Server does not start, see Troubleshooting Installation and Upgrade Problems.
        2. In a web browser, enter http://Server host:7180, where Server host is the fully qualified domain name or IP address of the host where the Cloudera Manager Server is running. The login screen for Cloudera Manager Admin Console displays.
        3. Log into Cloudera Manager Admin Console. The default credentials are: Username: admin Password: admin. Cloudera Manager does not support changing the admin username for the installed account. You can change the password using Cloudera Manager after you run the installation wizard. Although you cannot change the admin username, you can add a new user, assign administrative privileges to the new user, and then delete the default admin account.

        Choose Cloudera Manager Edition and Hosts

        Choose which edition of Cloudera Manager you are using and which hosts will run CDH and managed services.

        1. When you start the Cloudera Manager Admin Console, the install wizard starts up. Click Continue to get started.
        2. Choose which edition to install:
          • Cloudera Express, which does not require a license, but provides a limited set of features.
          • Cloudera Enterprise Data Hub Edition Trial, which does not require a license, but expires after 60 days and cannot be renewed.
          • Cloudera Enterprise with one of the following license types:
            • Basic Edition
            • Flex Edition
            • Data Hub Edition
          If you choose Cloudera Express or Cloudera Enterprise Data Hub Edition Trial, you can upgrade the license at a later time. See Managing Licenses.
        3. If you elect Cloudera Enterprise, install a license:
          1. Click Upload License.
          2. Click the document icon to the left of the Select a License File text field.
          3. Navigate to the location of your license file, click the file, and click Open.
          4. Click Upload.
          Click Continue to proceed with the installation.
        4. Information is displayed indicating what the CDH installation includes. At this point, you can access online Help or the Support Portal. Click Continue to proceed with the installation.
        5. Do one of the following depending on whether you are using Cloudera Manager to install software:
          • If you are using Cloudera Manager to install software, search for and choose hosts:
            1. To enable Cloudera Manager to automatically discover hosts on which to install CDH and managed services, enter the cluster hostnames or IP addresses. You can also specify hostname and IP address ranges. For example:
              Range Definition Matching Hosts
              10.1.1.[1-4] 10.1.1.1, 10.1.1.2, 10.1.1.3, 10.1.1.4
              host[1-3].company.com host1.company.com, host2.company.com, host3.company.com
              host[07-10].company.com host07.company.com, host08.company.com, host09.company.com, host10.company.com

              You can specify multiple addresses and address ranges by separating them by commas, semicolons, tabs, or blank spaces, or by placing them on separate lines. Use this technique to make more specific searches instead of searching overly wide ranges. The scan results will include all addresses scanned, but only scans that reach hosts running SSH will be selected for inclusion in your cluster by default. If you don't know the IP addresses of all of the hosts, you can enter an address range that spans over unused addresses and then deselect the hosts that do not exist (and are not discovered) later in this procedure. However, keep in mind that wider ranges will require more time to scan.

            2. Click Search. Cloudera Manager identifies the hosts on your cluster to allow you to configure them for services. If there are a large number of hosts on your cluster, wait a few moments to allow them to be discovered and shown in the wizard. If the search is taking too long, you can stop the scan by clicking Abort Scan. To find additional hosts, click New Search, add the host names or IP addresses and click Search again. Cloudera Manager scans hosts by checking for network connectivity. If there are some hosts where you want to install services that are not shown in the list, make sure you have network connectivity between the Cloudera Manager Server host and those hosts. Common causes of loss of connectivity are firewalls and interference from SELinux.
            3. Verify that the number of hosts shown matches the number of hosts where you want to install services. Deselect host entries that do not exist and deselect the hosts where you do not want to install services. Click Continue. The Select Repository screen displays.
          • If you installed Cloudera Agent packages in Install Cloudera Manager Agent Packages, choose from among hosts with the packages installed:
            1. Click the Currently Managed Hosts tab.
            2. Choose the hosts to add to the cluster.
        6. Click Continue.

        Choose the Software Installation Type and Install Software

        Choose a software installation type (parcels or packages) and install the software if not previously installed.

        1. Choose the software installation type and CDH and managed service version:
          • Use Parcels
            1. Choose the parcels to install. The choices depend on the repositories you have chosen; a repository can contain multiple parcels. Only the parcels for the latest supported service versions are configured by default.
              You can add additional parcels for previous versions by specifying custom repositories. For example, you can find the locations of the previous CDH 4 parcels at http://archive.cloudera.com/cdh4/parcels/. Or, if you are installing CDH 4.3 and want to use policy-file authorization, you can add the Sentry parcel using this mechanism.
              1. To specify the parcel directory, specify the local parcel repository, add a parcel repository, or specify the properties of a proxy server through which parcels are downloaded, click the More Options button and do one or more of the following:
                • Parcel Directory and Local Parcel Repository Path - Specify the location of parcels on cluster hosts and the Cloudera Manager Server host. If you change the default value for Parcel Directory and have already installed and started Cloudera Manager Agents, restart the Agents:
                  $ sudo service cloudera-scm-agent restart
                • Parcel Repository - In the Remote Parcel Repository URLs field, click the button and enter the URL of the repository. The URL you specify is added to the list of repositories listed in the Configuring Cloudera Manager Server Parcel Settings page and a parcel is added to the list of parcels on the Select Repository page. If you have multiple repositories configured, you see all the unique parcels contained in all your repositories.
                • Proxy Server - Specify the properties of a proxy server.
              2. Click OK.
            2. Select the release of Cloudera Manager Agent. You can choose either the version that matches the Cloudera Manager Server you are currently using or specify a version in a custom repository. If you opted to use custom repositories for installation files, you can provide a GPG key URL that applies for all repositories. Click Continue.
          • Use Packages - Do one of the following:
            • If Cloudera Manager is installing the packages:
              1. Click the package version.
              2. Select the release of Cloudera Manager Agent. You can choose either the version that matches the Cloudera Manager Server you are currently using or specify a version in a custom repository. If you opted to use custom repositories for installation files, you can provide a GPG key URL that applies for all repositories. Click Continue.
            • If you manually installed packages in Install CDH and Managed Service Packages, select the CDH version (CDH 4 or CDH 5) that matches the packages you installed manually.
        2. Select the Install Oracle Java SE Development Kit (JDK) checkbox to allow Cloudera Manager to install the JDK on each cluster host or leave deselected if you installed it. If checked, your local laws permit you to deploy unlimited strength encryption, and you are running a secure cluster, select the Install Java Unlimited Strength Encryption Policy Files checkbox. Click Continue.
        3. (Optional) Select Single User Mode to configure the Cloudera Manager Agent and all service processes to run as the same user. This mode requires extra configuration steps that must be done manually on all hosts in the cluster. If you have not performed the steps, directory creation will fail in the installation wizard. In most cases, you can create the directories but the steps performed by the installation wizard may have to be continued manually. Click Continue.
        4. If you chose to have Cloudera Manager install software, specify host installation properties:
          • Select root or enter the user name for an account that has password-less sudo permission.
          • Select an authentication method:
            • If you choose password authentication, enter and confirm the password.
            • If you choose public-key authentication, provide a passphrase and path to the required key files.
          • You can specify an alternate SSH port. The default value is 22.
          • You can specify the maximum number of host installations to run at once. The default value is 10.
        5. Click Continue. If you chose to have Cloudera Manager install software, Cloudera Manager installs the Oracle JDK, Cloudera Manager Agent, packages and CDH and managed service parcels or packages. During parcel installation, progress is indicated for the phases of the parcel installation process in separate progress bars. If you are installing multiple parcels, you see progress bars for each parcel. When the Continue button at the bottom of the screen turns blue, the installation process is completed.
        6. Click Continue. The Host Inspector runs to validate the installation and provides a summary of what it finds, including all the versions of the installed components. If the validation is successful, click Finish.

        Add Services

        Use the Cloudera Manager wizard to configure and start CDH and managed services.

        1. In the first page of the Add Services wizard, choose the combination of services to install and whether to install Cloudera Navigator:
          • Click the radio button next to the combination of services to install:
            CDH 4 CDH 5
            • Core Hadoop - HDFS, MapReduce, ZooKeeper, Oozie, Hive, and Hue
            • Core with HBase
            • Core with Impala
            • All Services - HDFS, MapReduce, ZooKeeper, HBase, Impala, Oozie, Hive, Hue, and Sqoop
            • Custom Services - Any combination of services.
            • Core Hadoop - HDFS, YARN (includes MapReduce 2), ZooKeeper, Oozie, Hive, Hue, and Sqoop
            • Core with HBase
            • Core with Impala
            • Core with Search
            • Core with Spark
            • All Services - HDFS, YARN (includes MapReduce 2), ZooKeeper, Oozie, Hive, Hue, Sqoop, HBase, Impala, Solr, Spark, and Key-Value Store Indexer
            • Custom Services - Any combination of services.
            As you select services, keep the following in mind:
            • Some services depend on other services; for example, HBase requires HDFS and ZooKeeper. Cloudera Manager tracks dependencies and installs the correct combination of services.
            • In a Cloudera Manager deployment of a CDH 4 cluster, the MapReduce service is the default MapReduce computation framework. Choose Custom Services to install YARN, or use the Add Service functionality to add YARN after installation completes.
                Note: You can create a YARN service in a CDH 4 cluster, but it is not considered production ready.
            • In a Cloudera Manager deployment of a CDH 5 cluster, the YARN service is the default MapReduce computation framework. Choose Custom Services to install MapReduce, or use the Add Service functionality to add MapReduce after installation completes.
                Note: In CDH 5, the MapReduce service has been deprecated. However, the MapReduce service is fully supported for backward compatibility through the CDH 5 lifecycle.
            • The Flume service can be added only after your cluster has been set up.
          • If you have chosen Data Hub Edition Trial or Cloudera Enterprise, optionally select the Include Cloudera Navigator checkbox to enable Cloudera Navigator. See the Cloudera Navigator Documentation.
          Click Continue.
        2. Customize the assignment of role instances to hosts. The wizard evaluates the hardware configurations of the hosts to determine the best hosts for each role. The wizard assigns all worker roles to the same set of hosts to which the HDFS DataNode role is assigned. You can reassign role instances if necessary.

          Click a field below a role to display a dialog containing a list of hosts. If you click a field containing multiple hosts, you can also select All Hosts to assign the role to all hosts, or Custom to display the pageable hosts dialog.

          The following shortcuts for specifying hostname patterns are supported:
          • Range of hostnames (without the domain portion)
            Range Definition Matching Hosts
            10.1.1.[1-4] 10.1.1.1, 10.1.1.2, 10.1.1.3, 10.1.1.4
            host[1-3].company.com host1.company.com, host2.company.com, host3.company.com
            host[07-10].company.com host07.company.com, host08.company.com, host09.company.com, host10.company.com
          • IP addresses
          • Rack name

          Click the View By Host button for an overview of the role assignment by hostname ranges.

        3. When you are satisfied with the assignments, click Continue.
        4. On the Database Setup page, configure settings for required databases:
          1. Enter the database host, database type, database name, username, and password for the database that you created when you set up the database.
          2. Click Test Connection to confirm that Cloudera Manager can communicate with the database using the information you have supplied. If the test succeeds in all cases, click Continue; otherwise, check and correct the information you have provided for the database and then try the test again. (For some servers, if you are using the embedded database, you will see a message saying the database will be created at a later step in the installation process.) The Review Changes screen displays.
        5. Review the configuration changes to be applied. Confirm the settings entered for file system paths. The file paths required vary based on the services to be installed. If you chose to add the Sqoop service, indicate whether to use the default Derby database or the embedded PostgreSQL database. If the latter, type the database name, host, and user credentials that you specified when you created the database.
            Warning: Do not place DataNode data directories on NAS devices. When resizing an NAS, block replicas can be deleted, which will result in reports of missing blocks.
          Click Continue. The wizard starts the services.
        6. When all of the services are started, click Continue. You see a success message indicating that your cluster has been successfully started.
        7. Click Finish to proceed to the Cloudera Manager Admin Console Home Page.

        Change the Default Administrator Password

        As soon as possible, change the default administrator password:
        1. Right-click the logged-in username at the far right of the top navigation bar and select Change Password.
        2. Enter the current password and a new password twice, and then click Update.

        Configure Oozie Data Purge Settings

        If you added an Oozie service, you can change your Oozie configuration to control when data is purged in order to improve performance, cut down on database disk usage, or to keep the history for a longer period of time. Limiting the size of the Oozie database can also improve performance during upgrades. See Configuring Oozie Data Purge Settings Using Cloudera Manager.

        Test the Installation

        You can test the installation following the instructions in Testing the Installation.

        Page generated August 17, 2015.