Install a cluster

Step 1. Precheck

Before installing a new cluster it is recommended to run the Precheck action. By doing this, you make sure that all necessary YUM repositories are available, the cluster doesn’t contain hosts with the same IP addresses, and all other prerequisites are met. Do the following:

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

    cluster precheck
    Running the cluster precheck
  2. Verify the requested action in the opened window.

    precheck verify
    Verifying the action
  3. Select the JOBS tab and wait until the running job is completed. After this, click the first item in the jobs list.

    precheck jobs
    Switching to the jobs list
  4. View the precheck results in the opened window. All tasks at the ansible [ check ] tab should have the [ Success ] status.

    precheck success
    Viewing the results
  5. If some tasks have the [ Fail ] status, you can expand their descriptions and see the detailed logs. Find the error reason, fix it, and run the Precheck action again.

Step 2. Run 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.

NOTE
In case of errors, you can find the logs at the JOBS tab.

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.

    cluster install
    Switching to the whole cluster installation
  2. Verify the requested action in the opened window. Notice that setting the Reboot cluster servers after installation flag leads to the hosts being reboot after the installation is completed. Otherwise, the reboot should be done manually.

    cluster install verify
    Verifying the action
  3. Wait until the job is completed.

  4. If some service fails during installation, but the preceding services are installed successfully, you can try to fix errors and restart installation of all the failed services. To do this, choose the Reinstall action in the Actions column at the CLUSTERS tab.

    cluster reinstall
    Installation restart

Single services

To install one or several cluster services manually, you should add these services to the cluster and then perform the actions described in the following subsections. The process of installing the ADB service differs from all other services.

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

ADB service

  1. Open the Services tab in the cluster menu. Find the row corresponding to the ADB service, click the icon in the Actions column, and choose the Install ADB action.

    service adb install
    Switching to installing ADB
  2. Verify the action in the opened window.

    service adb verify
    Verifying the action
  3. Wait until the job is completed. Then check that the ADB service state is changed from created to installed.

    service adb state1
    Checking the ADB service state after installing
  4. Click the icon in the Actions column again and choose the Init cluster action.

    service adb init
    Switching to initializing ADB
  5. Verify the action in the opened window.

    service adb init verify
    Verifying the action
  6. Wait until the job is completed. Then check that the ADB service state is changed from installed to initialized.

    service adb state2
    Checking the ADB service state after initializing

Other services

  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.

    install single service
    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 a new value, that is shown in the table New states of ADB services after installation.

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

  2. Chrony

  3. PXF

  4. ADB ClickHouse Connector

  5. ADB to Kafka

  6. Kafka to ADB

Step 3. Check 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 running.

    cluster state
    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 a new value that is shown in the table below.

    New states of ADB services after installation
    Service New state

    ADB

    initialized

    Chrony

    synced

    PXF

    installed

    ADB ClickHouse Connector

    installed

    ADB to Kafka

    installed

    Kafka to ADB

    installed

    services state
    The cluster services state after successful installation

Step 4. Create a default database

In order to create a default database for the new ADB cluster, perform the following actions:

  1. Open the Services tab in the cluster menu and select the Create database action in the drop-down list of actions, available for the ADB service.

    cluster default db
    Switching to creating a default database
  2. Verify the requested action in the opened window.

    verify default db
    Verifying the action
  3. Wait until the creating process is completed.

    NOTE
    In case of errors, you can find the logs at the JOBS tab.
  4. Make sure that the new database is successfully created. To do this:

    • Сonnect to the ADB Master Server (via SSH, etc.) and login under the default user name gpadmin.

      $ sudo su - gpadmin
    • List all ADB databases.

      psql -l

      The result:

                                     List of databases
         Name    |  Owner  | Encoding |  Collate   |   Ctype    |  Access privileges
      -----------+---------+----------+------------+------------+---------------------
       adb       | gpadmin | UTF8     | en_US.utf8 | en_US.utf8 | =Tc/gpadmin        +
                 |         |          |            |            | gpadmin=CTc/gpadmin
       diskquota | gpadmin | UTF8     | en_US.utf8 | en_US.utf8 |
       gpperfmon | gpadmin | UTF8     | en_US.utf8 | en_US.utf8 | gpadmin=CTc/gpadmin+
                 |         |          |            |            | =c/gpadmin
       postgres  | gpadmin | UTF8     | en_US.utf8 | en_US.utf8 |
       template0 | gpadmin | UTF8     | en_US.utf8 | en_US.utf8 | =c/gpadmin         +
                 |         |          |            |            | gpadmin=CTc/gpadmin
       template1 | gpadmin | UTF8     | en_US.utf8 | en_US.utf8 | =c/gpadmin         +
                 |         |          |            |            | gpadmin=CTc/gpadmin
      (6 rows)
Found a mistake? Seleсt text and press Ctrl+Enter to report it