See the EMC DSSD D5 document DSSD D5 Installation and Service Guide for more information about these tasks.

Cloudera recommends installing products using a package management tool such as yum for RHEL compatible systems. This tool depends 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.

To access the Cloudera Manager repository:

1. Download and save the Cloudera Manager repo file (cloudera-manager.repo ) from https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/cloudera-manager.repo):
2. Copy the repo file to the /etc/yum.repos.d/ directory.

In this step you install the JDK and Cloudera Manager Server packages on the Cloudera Manager host.

You can use Cloudera Manager to install the Oracle JDK and Cloudera Manager Agent or you can install them manually. To use Cloudera Manager to install the packages, you must meet the requirements described in Cloudera Manager Deployment.

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

  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.

1. Click the Cloudera Manager logo to open the Home page.
2. Click Administration > Settings.
3. Type DSSD in the Search box.
4. Select the DSSD Mode property.
5. Click Save Changes to commit the changes.

   Cloudera Manager reconfigures the system for DSSD mode, which may take several minutes.

6. Click the Cloudera Manager logo to open the Home page.
7. Click Add Cluster to continue with the installation.
8. The Cloudera Manager End User License Terms and Conditions page displays. Read the terms and conditions and then select Yes to accept them.
9. Click Continue.
10. The EMC Software License Agreement page displays. Read the terms and conditions and then select Yes to accept them.
11. Click Continue.

    The Welcome to Cloudera Manager page displays.

From the Welcome to Cloudera Manager page, you can select the edition of Cloudera Manager to install and, optionally, install a license:

1. 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.
2. 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. Go to the location of your license file, click the file, and click Open.
   4. Click Upload.
3. Information is displayed indicating what the CDH installation includes. At this point, you can click the Support drop-down menu to access online Help or the Support Portal.
4. Click Continue to proceed with the installation.

Choose which hosts will run CDH and managed services

1. 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 with 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 do not know the IP addresses of all of the hosts, you can enter an address range that spans over unused addresses and then clear 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. Clear host entries that do not exist and clear the hosts where you do not want to install services.
   • If you installed Cloudera Agent packages in Manually 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.
2. Click Continue.

   The Cluster Installation Select Repository screen displays.

1. Add the DSSD remote repository URL:
   1. Click the More Options button.
   2. In the Remote Parcel Repository URLs section, click the button.
   3. Enter the following URL in the blank field: http://cloudera-dssd.s3-website-us-west-1.amazonaws.com/dhp1/parcels/1.2
2. Choose the CDH and managed service version:
   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. Select the following parcels:
      • CDH 5
      • DSSD version 1.2
      • DSSD_SCR version 1.2 - This parcel enables short-circuit reads for HBase and Impala. Select this parcel even if you intend to disable short-circuit reads. (See DSSD D5 and Short-Circuit Reads.)
      • Any additional parcels required for your deployment (for example: Accumulo, Spark, or Keytrustee) .
      You can add additional parcels for previous versions by specifying custom repositories. For example, you can find the locations of the previous CDH 5 parcels at https://archive.cloudera.com/cdh5/parcels/.

      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. If you are using Cloudera Manager to install software, 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.
3. If you installed the Agent and JDK manually on all cluster hosts:
   • 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.

   • Skip the remaining steps in this section and continue with Add Services
4. Click Continue.

   The Cluster Installation JDK Installation Options screen displays.

5. Select Install Oracle Java SE Development Kit (JDK) to allow Cloudera Manager to install the JDK on each cluster host. If you have already installed the JDK, do not select this option. If 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.
     Note: If you already manually installed the JDK on each cluster host, this option to install the JDK does not display.
6. Click Continue.
7. (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.
8. Specify host installation properties:
   • Select root or enter the username 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.
9. 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.

10. Click Continue.

    The Cluster Installation page displays and shows the progress of the installation. When the Continue button turns blue, the cluster installation is complete.

11. 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.

1. In the first page of the Add Services wizard, choose the combination of services to install and whether to install Cloudera Navigator:
   • Select the combination of services to install:
     • Core Hadoop - HDFS, YARN (includes MapReduce 2), ZooKeeper, Oozie, Hive, and Hue
     • Core with HBase
     • Core with Impala
     • Core with Search
     • Core with Spark
     • All Services - HDFS, YARN (includes MapReduce 2), ZooKeeper, Oozie, Hive, Hue, 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 Cloudera Navigator 2 Overview.
2. Click Continue.
3. 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 DataNode role is only assigned to hosts that are connected to the DSSD D5. 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 box 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 box.

   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.

4. When you are satisfied with the assignments, click Continue.

From the Cluster Setup Review Changes page:

1. 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.

   The configuration properties that display on this page are somewhat different from those that display when configuring non-DSSD D5 DataNodes. Some properties, such as the DataNode directory have been removed because they do not apply to a cluster that uses DSSD D5 DataNodes. Other properties, such as the Flood Volume Name are specific to the DSSD D5 DataNode role.

2. (Required) In the Flood Volume Name field, enter the name of the Flood Volume as configured in the DSSD D5 appliance. If you are deploying multiple DSSD D5 appliances, note that you must specify this property for each appliance using a Role Group.
3. (Optional) If you are not using the entire capacity of the DSSD D5 for this cluster, set the Usable Capacity property. For most deployments, the default value (100 TB) is correct. See the EMC document DSSD Hadoop Plugin Installation Guide for more information on setting this property.
4. (Optional) Set the value of the HDFS Block Size parameter. The default value for this parameter is 512 MB when in DSSD Mode. You may want to change this for some types of work loads. See Tuning the HDFS Block Size for DSSD Mode .
5. 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.
8. If you see a message indicating that you need to restart Cloudera Management Services, restart the Cloudera Management Service:
   1. Do one of the following:
      • 1. Select Clusters > Cloudera Management Service > Cloudera Management Service.
        2. Select Actions > Restart.
      • On the Home > Status tab, click to the right of Cloudera Management Service and select Restart.
   2. Click Restart to confirm. The Command Details window shows the progress of stopping and then starting the roles.
   3. When Command completed with n/n successful subcommands appears, the task is complete. Click Close.
9. Choose Cluster > HDFS > Configuration and then in the filter section, select Scope > DSSD DataNode to view the DSSD D5 DataNode-specific properties.

   See the HDFS Properties in CDH 5.6.0 configuration reference for descriptions of these properties.

   See the EMC document DSSD Hadoop Plugin Installation Guide for information about setting these properties.

10. (Recommended for best performance) Set the Libflood CPU ID property.

    The value to use for this parameter should have been determined during the set up of the DSSD D5 appliance. See “Identify CPUs and NUMA Nodes” in the EMC document DSSD Hadoop Plugin Installation Guide. The value you set for this parameter can effect the performance of your cluster.

11. (Optional) Set the following properties to tune the performance of your cluster:
    • Libflood Command Queues
    • Libflood Command Queue Depth
12. (Optional) Set the Java heap size for the NameNode.
    1. Choose Clusters > HDFS > Configuration.
    2. Type Java heap in the search box.
    3. Set the Java Heap Size of NameNode in Bytes parameter:

       Cloudera Manager automatically sets the value of this parameter to 4 GB (If there are not adequate resources in the cluster, Cloudera Manager may set a smaller value.) Cloudera recommends that you manually set the value of this parameter by calculating the number of HDFS blocks in the cluster and including 1 GB of Java heap for each 1 million HDFS blocks. For more information on HDFS block size and the DSSD D5, see Tuning the HDFS Block Size for DSSD Mode .

    4. Set the Java Heap Size of Secondary NameNode in Bytes parameter to the same value as the Java Heap Size of NameNode in Bytes parameter.
    5. Restart the NameNode:
       1. Choose Clusters > HDFS > Instances.
       2. In the table of roles, select the NameNode (Active) and SecondaryNameNode role types.
       3. Click Actions for Selected > Restart.

If you added an Oozie service, you can change your Oozie configuration to control when data is purged 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.

  Note: The steps in this section allow you to map DataNode hosts to racks based on how the hosts are connected to the DSSD D5 and assume that all the previous installation steps on this page have been completed.

To increase capacity and performance, you can configure a cluster that uses multiple DSSD D5 storage appliances. You configure the cluster by assigning all hosts connected to a DSSD D5 appliance to a single "rack" and select one of three modes to provide policies used by the NameNode to satisfy the configured replication factor. If you are only configuring a single DSSD D5 appliance, skip this section.

You can also move hosts between appliances. See Moving Existing Hosts to a New DSSD D5

  Note: The replication factor is a configuration you set on the HDFS service. To set or view this configuration, go to the HDFS service and select Configuration > Replication Factor.

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