Cluster installing

Step 1. Running installation

There are two ways of cluster services installation:

  1. Whole cluster. In this method all services are installed automatically one by one after applying the Install action to the 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 into the already deployed cluster.

In both cases each service starts automatically after the installation.

Whole cluster

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

  1. Apply the Install action to the cluster selected at the CLUSTERS tab.

    adcm services install 02
    Switching to the whole cluster installation
  2. Verify the requested action in the opened window.

    verify install
    Verifying 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.

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 in the cluster menu. For each service that should be installed, click the icon in the Actions column and choose the Install action.

    adcm services install 01
    Switching to installing single services
  2. Verify the action in the opened window.

    verify install
    Verifying 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.


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. Viewing the results of installation

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 at the JOBS tab.

The status of ADCM jobs is displayed in the upper-right corner of the web interface. The yellow circle represents the number of running jobs, and the green and red circles represent the number of successfully and unsuccessfully completed jobs, respectively. You can move to the necessary block of jobs by clicking at the corresponding circle.
adcm services install 04
The JOBS tab

The successful completion of the service installation is determined by the transition of the job from the running status to the success status at the JOBS tab. 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 at the JOBS tab.

adcm services install 06
Switching to a job page

A job page contains two sections displayed at the left side of the screen: 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.

adcm services install 07
A job page

Step 3. Checking the cluster state after 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 at the CLUSTERS tab, is being changed from created to installed.

    adcm services install 09
    The cluster state after successful installation
  • The state of cluster services, displayed in the cluster menu at the Services tab, is being changed from created to installed.

    adcm services install 08
    The cluster services state after successful installation
Features of Hive installing

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. It is called MySQL in the list of services. So, you can install and configure it, using ADCM.

In addition to configuring the MySQL/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 MySQL/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