This is the documentation for Cloudera Manager 4.8.4.
Documentation for other versions is available at Cloudera Documentation.

Installation Path B - Installation Using Your Own Method

To manage the installation of packages yourself, follow the instructions in this section. If you have already installed Cloudera Manager and CDH, skip this section and continue on to other installation tasks. For example, if you have already completed a Path A installation, you might Specify the Racks for Hosts or Test the Installation next.

  Note:

You can also use Puppet or Chef to install packages on your cluster.

The general steps in this procedure for Installation Path B are:

Before You Begin

Cloudera Manager and Cloudera Distribution of Hadoop (CDH) are comprised of a set of services. These services interact among each other and use databases to complete tasks. The parts that make up this system are very flexible, so you could deploy these services and resources in many different ways, though the process is greatly simplified by following Cloudera's installation and configuration guidelines.

Considering this, Cloudera recommends you begin by establishing a foundation of database resources that can be utilized as they become necessary throughout the installation process. Begin by deploying the necessary supporting services and then proceeding through the installation process.

Install the Oracle JDK

Install the Oracle Java Development Kit (JDK) on each of your cluster hosts where you want to run Hadoop before installing Cloudera's packages. Cloudera Manager can manage both CDH3 and CDH4 hosts, and the required JDK version varies accordingly.

  • For installation instructions and recommendations for CDH3, see the topic on Java Development Kit Installation in the CDH3 Installation Guide.
  • For installation instructions and recommendations for CDH4, see the topic on Java Development Kit Installation in the CDH4 Installation Guide.

Install Databases for the Cloudera Manager Services

Create and configure databases for the Cloudera Manager Monitoring Services (Activity Monitor, Service Monitor, Report Manager, and Host Monitor), and for the Hive Metastore and Cloudera Navigator. Cloudera supports various database solutions including the PostgreSQL embedded database, PostgreSQL external databases, MySQL databases, or Oracle databases.

Information about how these databases are set up in your environment is required to complete the CDH and Cloudera Manager configuration. The details of what is required varies among database types. Gather this information either as you complete the installations or from database administrators who have the information required. A list of what information is required for each database type is provided in each database section.

Follow the instructions at Installing and Configuring Databases to complete this task.

Database choices Notes and Instructions
Option A: Embedded PostgreSQL This is the same PostgreSQL application and database that the Cloudera Manager wizard installs. For installation and configuration instructions, see Installing an Embedded PostgreSQL Database.
Option B: External PostgreSQL After PostgreSQL is installed, you need to run a script to prepare a database for the Cloudera Manager Server as described in Installing and Configuring an External PostgreSQL Database.
Option C: External MySQL You can use the same MySQL application that is used for the monitoring and reporting features, as described in Installing and Configuring a MySQL Database. After MySQL is installed, you need to run a script to prepare a database for the Cloudera Manager Server, as is described later in this topic.
Option D: External Oracle You can use an external Oracle database for monitoring and reporting features, as described in Using an Oracle Database.

Step 1: Establish Your Repository Strategy

Cloudera recommends installing products using package management tools such as yum for Red Hat Enterprise Linux (RHEL) or CentOS, zypper for SUSE, or 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 CDH and Cloudera Manager include using:

  Note:

The instructions that follow assume you are adding a CDH4 repository; if you are installing CDH3, modify the commands accordingly with the correct standard repository and repo file paths as found in CDH Version and Packaging Information.

On Red Hat-compatible Systems

To add the CDH4 Yum repository:

Click the entry in the table at CDH Download Information that matches your Red Hat or CentOS system, navigate to the repo file (cloudera-cdh4.repo) for your system and save it in the /etc/yum.repos.d/ directory.

To add the Cloudera Manager Yum repository: Navigate to the Cloudera Manager repo file (cloudera-manager.repo) for your system and save it in the /etc/yum.repos.d/ directory.

To optionally add a Repository key:

  • For Red Hat/CentOS/Oracle 5 systems:
$ sudo rpm --import http://archive.cloudera.com/cdh4/redhat/5/x86_64/cdh/RPM-GPG-KEY-cloudera 
  • For Red Hat/CentOS 6 systems:
$ sudo rpm --import http://archive.cloudera.com/cdh4/redhat/6/x86_64/cdh/RPM-GPG-KEY-cloudera 

On SLES Systems

To add the CDH4 and Cloudera Manager repositories:

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

To optionally add a Repository key:

$ sudo rpm --import http://archive.cloudera.com/cdh4/sles/11/x86_64/cdh/RPM-GPG-KEY-cloudera  

On Ubuntu or Debian Systems

To add the CDH4 repositories:

  1. Click the entry in the table at CDH Version and Packaging Information that matches your Ubuntu or Debian system
  2. Navigate to the Cloudera Manager list file (cloudera.list) for your system and save it in the /etc/apt/sources.list.d/ directory.

To add the Cloudera Manager repositories:

  1. Click the entry in the table at Cloudera Manager Version and Download Information that matches your Ubuntu or Debian system
  2. Navigate to the Cloudera Manager list file (cloudera.list)
  3. Copy the content of that file and append it to the content of the cloudera.list you just saved in the /etc/apt/sources.list.d/ directory.

To optionally add a Repository key:

  • For Ubuntu Lucid systems:
$ curl -s http://archive.cloudera.com/cdh4/ubuntu/lucid/amd64/cdh/archive.key | sudo apt-key add -
  • For Ubuntu Precise systems:
$ curl -s http://archive.cloudera.com/cdh4/ubuntu/precise/amd64/cdh/archive.key | sudo apt-key add -
  • For Debian Squeeze systems:
$ curl -s http://archive.cloudera.com/cdh4/debian/squeeze/amd64/cdh/archive.key | sudo apt-key add -

Step 2: Install CDH

This section describes how to install CDH on RHEL, CentOS, SUSE, and Debian/Ubuntu systems. This installation is done in preparation for using Cloudera Manager to configure and manage your cluster. For information about installing CDH, see the CDH4 Installation Guide.

  Important: The Activity Monitor in Cloudera Manager 4.0 requires the hue-plugins package to be installed on the JobTracker host, regardless of whether you are using Hue. If you are using Hue, the hue-plugins package must be installed on all hosts.

On Red Hat-compatible Systems (RHEL/CentOS/Oracle)

  1. Install packages on every host in your cluster:

    For CDH4:

    $ 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

    For CDH3:

    $ sudo yum -y install hadoop-0.20 hadoop-0.20-native.x86_64 hadoop-0.20-sbin.x86_64 hue-plugins hadoop-zookeeper hadoop-hbase oozie oozie-client
  2. (Requires CDH 4.2 or later) Install Impala and the Impala Shell on Impala machines:
    $ sudo yum -y install impala impala-shell
  3. (Requires CDH 4.3 or later) Install the Solr Server on machines where you want Cloudera Search.
    $ sudo yum -y install solr-server
  4. To install the hue-common package and all Hue applications on the Hue machine, install the hue meta-package:
    $ sudo yum install hue 
  5. Disable autostart for Hue on the Hue machine, and for Oozie on every machine on which it is installed.
      Note:

    Preventing Hue from starting is only required on CDH3u5 and earlier. If you are running CDH4 or a version of CDH3 newer than CDH3u5, you do not need to prevent Hue from starting. While stopping Hue from starting is not required in those cases, executing the chkconfig command generates an error, but there are no other negative effects.

    $ sudo /sbin/chkconfig hue off 
    $ sudo /sbin/chkconfig oozie off 
    $ sudo /sbin/chkconfig hadoop-httpfs off

On SLES Systems

  1. Install packages on every host in your cluster:

    For CDH4:

    $ 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

    For CDH3:

    $ sudo zypper install hadoop-0.20 hadoop-0.20-native.x86_64 hadoop-0.20-sbin.x86_64 hue-plugins hadoop-zookeeper hadoop-hbase oozie oozie-client
  2. (Requires CDH 4.2 or later) Install Impala and the Impala Shell on Impala machines:

    On 64-bit SUSE systems:

    $ sudo zypper install impala impala-shell
  3. (Requires CDH 4.3 or later) Install the Solr Server on machines where you want Cloudera Search.
    $ sudo zypper install solr-server
  4. To install the hue-common package and all Hue applications on the Hue machine, install the hue meta-package:
    $ sudo zypper install hue 
  5. Disable autostart for Hue on the Hue machine, and for Oozie on every machine on which it is installed.
      Note:

    Preventing Hue from starting is only required on CDH3u5 and earlier. If you are running CDH4 or a version of CDH3 newer than CDH3u5, you do not need to prevent Hue from starting. While stopping Hue from starting is not required in those cases, executing the chkconfig command generates an error, but there are no other negative effects.

    $ sudo /sbin/chkconfig hue off 
    $ sudo /sbin/chkconfig oozie off 
    $ sudo /sbin/chkconfig hadoop-httpfs off

On Ubuntu or Debian Systems

  1. Install packages on every host in your cluster:

    For CDH4:

    $ 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

    For CDH3:

    $ sudo apt-get install hadoop-0.20 hadoop-0.20-native.x86_64 hadoop-0.20-sbin.x86_64 hue-plugins hadoop-zookeeper hadoop-hbase oozie oozie-client
  2. (Requires CDH 4.2 or later) Install Impala and the Impala Shell on Impala machines:

    On 64-bit systems:

    $ sudo apt-get install impala impala-shell
  3. (Requires CDH 4.3 or later) Install the Solr Server on machines where you want Cloudera Search.
    $ sudo apt-get install solr-server
  4. To install the hue-common package and all Hue applications on the Hue machine, install the hue meta-package:
    $ sudo apt-get install hue 
  5. Stop hadoop-httpfs.
    service hadoop-httpfs stop
  6. Disable autostart for Hue on the Hue machine, and for Oozie on every machine on which it is installed.
      Note:

    Preventing Hue from starting is only required on CDH3u5 and earlier. If you are running CDH4 or a version of CDH3 newer than CDH3u5, you do not need to prevent Hue from starting. While stopping Hue from starting is not required in those cases, executing the chkconfig command generates an error, but there are no other negative effects.

    $ sudo update-rc.d -f hue remove 
    $ sudo update-rc.d -f oozie remove
    $ sudo update-rc.d -f hadoop-httpfs remove

Step 3: Install the Cloudera Manager Server

Install the Cloudera Manager Server either on the machine where the database is installed, or on a machine that has access to the database. This machine need not be a host in the cluster that you want to manage with Cloudera Manager. The Cloudera Manager Server does not require CDH4 to be installed on the same machine.

On the Cloudera Manager Server machine, type the following commands to install the Cloudera Manager packages.

To install Cloudera Manager on a RHEL system if you have a yum repo configured:

$ sudo yum install cloudera-manager-daemons 
$ sudo yum install cloudera-manager-server

To install Cloudera Manager on a RHEL system if you're transferring RPMs manually:

$ sudo yum --nogpgcheck localinstall cloudera-manager-daemons-*.rpm
$ sudo yum --nogpgcheck localinstall cloudera-manager-server-*.rpm

To install Cloudera Manager Server on a SUSE system:

$ sudo zypper install cloudera-manager-daemons cloudera-manager-server

To install Cloudera Manager Server on a Debian/Ubuntu system:

$ sudo apt-get install cloudera-manager-daemons cloudera-manager-server

Step 4: Configure a Database for the Cloudera Manager Server

To manage the services, Cloudera Manager Agents, and configurations in your cluster, the Cloudera Manager Server stores data in a database. You can either use an existing database or install a new database. After installing the database, you must then run a script to prepare that database for use with the Cloudera Manager Server.

  Note:

The Cloudera Manager Server database is separate from the databases used by the Cloudera Manager Activity Monitor, Service Monitor, Report Manager, Host Monitor, Hive Metastore, and Cloudera Navigator. You should have installed these services' databases in the prerequisites.

In this release, you can use any one of the database options listed in the table above.

  Important:

You should deploy only one of the database options listed below. After establishing one database for the Cloudera Manager server, move on to step 5.

Installing the embedded PostgreSQL database package on the Cloudera Manager Server host:

  1. Install the PostgreSQL database:
    • On a Red Hat system if you have a yum repo configured:
      $ sudo yum install cloudera-manager-server-db
    • On a Red Hat system if you're transferring RPMs manually:
      $ sudo yum --nogpgcheck localinstall cloudera-manager-server-db.noarch.rpm
    • On a SUSE system:
      $ sudo zypper install cloudera-manager-server-db
    • On a Debian/Ubuntu system:
      $ sudo apt-get install cloudera-manager-server-db
  2. Start the PostgreSQL database:
    $ sudo service cloudera-scm-server-db start

Preparing a Custom Database for the Cloudera Manager Server

If you have elected not to use the embedded database, the Cloudera Manager server database configuration can be completed using the scm_prepare_database.sh script, which is installed in the /usr/share/cmf/schema directory on the host where the Cloudera Manager Server package is installed. You must run the script on the Cloudera Manager Server host.

Note: If you are not using the embedded database, remove /etc/cloudera-scm-server/db.mgmt.properties.

After you have installed your database application or collected information about an existing Oracle installation, use the scm_prepare_database.sh script to prepare the database for use with the Cloudera Manager Server. This script enables Cloudera Manager Server to connect to an external database in MySQL, PostgreSQL, or Oracle. The script prepares the database by:

  • Creating the Cloudera Manager Server database configuration file.
  • Creating a database for the Cloudera Manager Server to use. This is optional and is only completed if options are specified.
  • Setting up a user account for the Cloudera Manager Server. This is optional and is only completed if options are specified.

Script syntax

scm_prepare_database.sh [options] database-type database-name username password

Required Parameter

Description

database-type

To connect to a MySQL database, specify mysql as the database type. To connect to an Oracle database, specify oracle. To connect to an external PostgreSQL database, specify postgresql.

database-name

The name of the Cloudera Manager Server database you want to create.

username

The username for the Cloudera Manager Server database you want to create.

password

The password for the Cloudera Manager Server database you want to create. If you don't specify the password on the command line, the script will prompt you to enter it.

Option

Description

-h or --host

The IP address or hostname of the host where MySQL or Oracle is installed. The default is to use the local host.

-P or --port

The port number to use to connect to MySQL or Oracle. The default port is 3306. This option is used for a remote connection only.

-u or --user

The username for the MySQL or Oracle application. The default is root.

-p or --password

The password for the MySQL or Oracle application. The default is no password.

--scm-host

The hostname where the Cloudera Manager Server is installed. Omit if the Cloudera Manager server and MySQL or Oracle are installed on the same host.

--config-path

The path to the Cloudera Manager Server configuration files. The default is /etc/cloudera-scm-server.

--schema-path

The path to the Cloudera Manager schema files. The default is /usr/share/cmf/schema (the location of the script).

-f

The script will not stop if an error is encountered.

-? or --help

Display help.

  Note:

You can also run scm_prepare_database.sh without options to see the syntax.

Run the script that applies to the type of database you have installed.

Example 1: Running the script when MySQL is installed on another host

This example explains how to run the script on the Cloudera Manager Server machine (myhost2) and create and use a temporary MySQL user account to connect to MySQL remotely on the MySQL machine (myhost1).

  1. On myhost1's MySQL prompt, create a temporary user who can connect from myhost2:
    mysql> grant all on *.* to 'temp'@'%' identified by 'temp' with grant option;
    Query OK, 0 rows affected (0.00 sec)
  2. On the Cloudera Manager Server host (myhost2), run the script:
    $ sudo /usr/share/cmf/schema/scm_prepare_database.sh mysql -h myhost1.sf.cloudera.com -utemp -ptemp --scm-host myhost2.sf.cloudera.com scm scm scm
    Looking for MySQL binary
    Looking for schema files in /usr/share/cmf/schema
    Verifying that we can write to /etc/cloudera-scm-server
    Creating SCM configuration file in /etc/cloudera-scm-server
    Executing: /usr/java/jdk1.6.0_31/bin/java -cp /usr/share/java/mysql-connector-java.jar:/usr/share/cmf/schema/../lib/* com.cloudera.enterprise.dbutil.DbCommandExecutor /etc/cloudera-scm-server/db.properties com.cloudera.cmf.db.
    [ main] DbCommandExecutor INFO Successfully connected to database.
    All done, your SCM database is configured correctly!
  3. On myhost1, delete the temporary user:
    mysql> drop user 'temp'@'%';
    Query OK, 0 rows affected (0.00 sec)

Example 2: Running the script to configure Oracle

This shows an example of running the script to configure an Oracle database.

[root@rhel55-6 ~]# /usr/share/cmf/schema/scm_prepare_database.sh -h cm-oracle.example.com oracle orcl sample_user sample_pass
Verifying that we can write to /etc/cloudera-scm-server
Creating SCM configuration file in /etc/cloudera-scm-server
Executing: /usr/java/jdk1.6.0_31/bin/java -cp /usr/share/java/mysql-connector-java.jar:/usr/share/cmf/schema/../lib/* com.cloudera.enterprise.dbutil.DbCommandExecutor /etc/cloudera-scm-server/db.properties com.cloudera.cmf.db.
[ main] DbCommandExecutor INFO Successfully connected to database.
All done, your SCM database is configured correctly!

Example 3: Running the script when PostgreSQL is collocated with the Cloudera Manager Server

This example explains how to run the script on the Cloudera Manager Server machine when you have installed PostgreSQL on the same machine.

$ /usr/share/cmf/schema/scm_prepare_database.sh postgresql -upostgres scm scm scm

Retrieving the Database Host, User Name, or Password

After you are finished installing Cloudera Manager, you can retrieve the Cloudera Manager server database host, user name or password, if necessary, by reading the /etc/cloudera-scm-server/db.properties file:

# cat /etc/cloudera-scm-server/db.properties

Auto-generated by scm_prepare_database.sh
#
Sat Oct 1 12:19:15 PDT 201
#
com.cloudera.cmf.db.type=mysql
com.cloudera.cmf.db.host=localhost:7432
com.cloudera.cmf.db.name=scm
com.cloudera.cmf.db.user=scm
com.cloudera.cmf.db.password=TXqEESuhj5

Step 5: Install the Cloudera Manager Agents

  Important:

It is recommended that you install CDH before installing the Cloudera Manager Agents.

In this step, you will install the Cloudera Manager Agents and the /etc/cloudera-scm-agent/config.ini configuration file on every machine in your cluster that you want to manage using Cloudera Manager. You can use whatever method you currently use to install software and configuration files on your cluster nodes.

On every Cloudera Manager Agent host machine (including those that will run one or more of the Cloudera Manager Services: Service Monitor, Activity Monitor, Event Server, Alert Publisher, Report Manager), use the following commands to install the Cloudera Manager packages:

To install the Cloudera Manager Agent and Services on a RHEL system if you have a yum repo configured:

$ sudo yum install cloudera-manager-agent cloudera-manager-daemons

To install the Cloudera Manager Agent and Services on a RHEL system if you're transferring RPMs manually:

$ sudo yum --nogpgcheck localinstall cloudera-manager-agent-package.*.x86_64.rpm cloudera-manager-daemons

To install the Cloudera Manager Agent and Services on a SUSE system:

$ sudo zypper install cloudera-manager-agent cloudera-manager-daemons

To install the Cloudera Manager Agent and Services on a Debian/Ubuntu system:

$ sudo apt-get install cloudera-manager-agent cloudera-manager-daemons

On every Cloudera Manager Agent host machine, 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 host machine where the Server is running
server_port Port on host machine where the Server is running

Step 6: 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 you are, shut down HDFS and MapReduce (service hadoop-0.20-<daemon> stop), and configure the init scripts to not start on boot (for example, chkconfig hadoop-0.20-<daemon> off). Contact Cloudera Support for help converting your existing Hadoop configurations for use with Cloudera Manager.
  1. Type this command on the Cloudera Manager Server machine:
    $ sudo service cloudera-scm-server start
  2. If you have problems starting the Server, such as database permissions problems, you can use the Server's log /var/log/cloudera-scm-server/cloudera-scm-server.log to troubleshoot the problem.
      Note: If the Server fails to start, and you are using MySQL to store information about service configuration, check that the InnoDB engine is configured, not the MyISAM engine; the server will not start if its tables are configured with the MyISAM engine, and an error such as the following will appear in the log file:
    Tables ... have unsupported engine type ... .  InnoDB is required. 

    For more information, see Installing and Configuring a MySQL Database .

Step 7: Start the Cloudera Manager Agents

Run this command on each Agent machine:

$ sudo service cloudera-scm-agent start

When the Agent starts up, it contacts the Cloudera Manager Server. When the Agent machines reboot, cloudera-scm-agent will start automatically.

Troubleshooting Cloudera Manager Agent Connection Problems

If there is a communication failure between a Cloudera Manager Agent and Cloudera Manager Server, you can use the Cloudera Manager Server log file /var/log/cloudera-scm-server/cloudera-scm-server.log and the Cloudera Manager Agent log files /var/log/cloudera-scm-agent/cloudera-scm-agent.log to troubleshoot the problem. The following is a common error.

Error message

Description

error: (113, 'No route to host') in cloudera-scm-agent.log.

This indicates that the agent is unable to connect to the Cloudera Manager Server. Make sure that iptables and SELinux are both turned off.

Step 8: Start the Cloudera Manager Admin Console

The Cloudera Manager Admin Console enables you to use Cloudera Manager to configure, manage, and monitor Hadoop on your cluster. Before using the Cloudera Manager Admin Console, gather information about the server's URL and port.

The server URL takes the following form:

http://<Server host>:<port>

<Server host> is the fully-qualified domain name or IP address of the host machine where the Cloudera Manager Server is installed. <port> is the port configured for the Cloudera Manager Server. The default port is 7180. For example, use a URL such as the following:

http://myhost.example.com:7180/

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 wizard in the next section. While 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.

To start the Cloudera Manager Admin Console:

  1. In a web browser, enter the URL, including the port, for the Cloudera Server. The login screen for Cloudera Manager appears.
  2. Log into Cloudera Manager. The default credentials are: Username: admin Password: admin

Step 9: Configure Services

The following instructions describe how to use the Cloudera Manager wizard to configure and start the Hadoop services.

  1. When you start the Cloudera Manager Admin Console, the install wizard starts up. Click Continue to get started.
  2. Browse to your Cloudera Manager License file. If you don't install it now, Cloudera Manager Standard Edition will be installed. You can also elect to install the 60-day Trial Edition that gives you access to the full set of Enterprise features for 60 days.
  3. If you install a Cloudera Manager license, you must restart the Cloudera Manager server. From the command line, enter:
    $ sudo service cloudera-scm-server restart
  4. After the Cloudera Manager server restarts, log in again.
      Note:

    After restarting the server, wait a few seconds for the server to finish initializing before you try to reconnect to the Admin Console.

  5. Click Continue in the next screen.
  6. On the "Specify hosts..." page, click the Currently Managed Hosts tab (you have already installed CDH4 and Cloudera Manager components) and choose the hosts to add to your cluster.
  7. On the "Select Repository" page, choose Use Packages, as you have already used packages earlier in this process.
  8. On the "Host Inspector" page, review the validation results and correct any issues that may have been identified.
  9. Choose the Hadoop services you want to start. You can choose one of the standard combinations: Core Hadoop, Real-Time Delivery (previously known as HBase Services), Real-Time Query (which includes HDFS, Hive and Impala), or All Services; these combinations take into account the dependencies between the Hadoop services. Alternatively, you can choose Custom Services, and select the services individually.
      Note: Some services depend on others; for example, HBase requires HDFS and ZooKeeper.

    The Cloudera Management Services, which are added to each package, are Cloudera Manager processes that run to support monitoring and management features in Cloudera Manager. Cloudera Navigator is a system to support enforcement of compliance with company policies for data stored in a Hadoop Distributed File System (HDFS) deployment.

  10. On the Database Setup page, enter the information requested. You will need to provide information for the Activity Monitor, Service Monitor, Report Manager, Host Monitor, and Hive metastore databases.
      Important: The value you enter as the database hostname must match the value you entered for the hostname (if any) when you created the database (see Installing and Configuring Databases).

    For example, if you entered the following for the Activity Monitor database:

    mysql> grant all on amon.* TO 'amon'@'localhost' IDENTIFIED BY 'amon_password';

    the value you enter here for the database hostname must be localhost.

    On the other hand, if you had entered the following when you created the database

    mysql> grant all on amon.* TO 'amon'@'myhost1.myco.com' IDENTIFIED BY 'amon_password';

    the value you enter here for the database hostname must be myhost1.myco.com.

    If you did not specify a host, or used a wildcard to allow access from any host, you can enter either the fully-qualified domain name (FQDN) here, or localhost. For example, if you entered

    mysql> grant all on amon.* TO 'amon'@'%' IDENTIFIED BY 'amon_password';

    the value you enter here for the database hostname can be either the FQDN or localhost. Similarly, if you entered

    mysql> grant all on amon.* TO 'amon' IDENTIFIED BY 'amon_password';

    the value you enter here for the database hostname can be either the FQDN or localhost.

  11. Click Test Connection to confirm that Cloudera Manager can communicate with the databases using the information you have supplied. This atypical transaction takes two heartbeats to complete (about 30 seconds with the default heartbeat interval). If the test succeeds in all cases, click Continue; otherwise check and correct the information you have provided for the databases and then try the test again.
  12. Confirm the settings entered for file system paths, such as the NameNode Data Directory and the DataNode Data Directory.
  13. Supply the name of the mail server (it can be localhost), the mail server user, and the mail recipients.
  14. Click Continue. The wizard starts the services on your cluster.
  15. When all of the services are started, click Continue.
  16. Click Continue.

Step 10: Change the Default Administrator Password

As soon as possible after running the wizard and beginning to use Cloudera Manager, you should change the default administrator password.

  1. From the Administration tab, select Users.
  2. Click the Change Password button next to the admin account.
  3. Enter a new password twice and then click Submit.

Step 11: Test the Installation

For testing instructions, see Testing the Installation.

  Note: If you change the hostname or port where the Cloudera Manager is running, or you enable TLS security, you must restart the Cloudera Management Services to update the URL to the Server. For instructions, see Restarting a Service.