Install a cluster

Eugenia Kuzina, Daria Barysheva

Step 1. Installation

There are two ways to install cluster services:

  1. Whole cluster. In this method all services are installed automatically one by one after applying the Install action to a cluster.

  2. Single services. In this method each service is installed manually after applying one or more actions to it. This way is also suitable for installing new services in the already deployed cluster.

In both cases each service starts automatically after installation.

IMPORTANT
The installation must be performed on a clean host without prior installation of related or similar software.

Whole cluster

To install all cluster services within a single action, follow the steps:

  1. Apply the Install action to the cluster selected on the Clusters page by clicking the actions default dark actions default light icon in the Actions column.

    Switch to the whole cluster installation
    Switch to the whole cluster installation

  2. Verify the requested action in the opened window.

    Verify the action
    Verify the action

  3. Wait until the job is completed.

Single services

To install one or several cluster services manually, you should add these services to the cluster and then perform the actions described below.

CAUTION
Notice that services are installed one by one. Do not install another service until the installation of the previous one is completed.

  1. Open the Services tab on the cluster page. For each service that should be installed, click the actions default dark actions default light icon in the Actions column and select the Install action.

    Switch to installation of single services
    Switch to installation of single services

  2. Verify the action in the opened window.

    Verify the action
    Verify the action

  3. Wait until the job is completed. Then check that the service state has changed from created to installed.

  4. Repeat the previous actions for other services that should be installed.

IMPORTANT

When you install services manually, one by one, use the following order:

  1. Zookeeper

  2. HDFS

  3. YARN

  4. HBase

  5. Hive

  6. Spark

  7. Monitoring

Step 2. View installation results

ADCM starts a single job for installation process, as well as for any other task. You can find out about the status of jobs more specifically on the Jobs page.

The Jobs page
The Jobs page

The successful completion of the service installation is determined by the transition of the job from the running status to the success status on the Jobs page. If the job fails, it switches to the failed status. In this case it is possible to see more detailed information about the errors that occurred via clicking the failed job on the Jobs page. The window with job inner steps is opened. Click the ellipsis in the Details column for additional information on the current step.

Switch to a job page
Switch to job details

A job page contains two sections: ansible [ stdout] and ansible [ stderr ]. These are technical logs of the job that include information from standard I/O streams stdout/stderr. These logs can help to understand what caused the problems.

There can also be the optional third section ansible [ check ]. These are the logs of the most frequent errors checks. The description of these errors is more simple and specific, than in two previous technical logs.

The contents of all three sections should be studied if errors occur.

Job page
Job details

Step 3. Check the cluster state after the installation

As a result of successful installation, the cluster and its services change their state according to the following rules:

  • The cluster state, displayed in the State field on the Clusters page, is being changed from created to installed.

    The cluster state after successful installation
    The cluster state after successful installation

  • The state of cluster services, displayed on the Services tab of the cluster page, is being changed from created to installed.

    The state of cluster services after successful installation
    The state of cluster services after successful installation
Hive installation features

 
The Metastore component of the Hive service requires the installed MySQL/MariaDB database and the ability to access it. The MariaDB service is included into the ADH bundle. So, you can install and configure it, using ADCM.

In addition to configuring the MariaDB service itself, you should also configure the appropriate GRANT accesses to be used by the Hive service. For example, the simplest case of granting access looks like this:

GRANT ALL ON *.* TO 'root'@'<metastore_fqdn>' identified by '<password>' WITH GRANT OPTION;

 — where <metastore_fqdn> and <password> should be replaced by real data of the MariaDB server.

You can specify the address and credentials for connecting to the database in the Hive configuration.

Found a mistake? Seleсt text and press Ctrl+Enter to report it