Configure a cluster

Daria Barysheva
IMPORTANT
There is usually no need to change cluster configuration parameters. You can leave all parameters at the default values.

After creation a new cluster, you can configure it by performing the following steps:

  1. Select a cluster on the Clusters page. To do this, click a cluster name in the Name column.

    Select a cluster
    Select a cluster

  2. Open the Configuration tab on the cluster page and switch on the Show advanced toggle.

  3. Fill in all necessary parameters and click Save.

Cluster configuration parameters are listed below:

  • Paths to the repositories that are used during the installation process depending on the cluster operating system (AltLinux, CentOS, Astra Linux). Only the marked repositories are registered on the cluster servers.

    Altlinux 8 repositories
    Parameter Description

    Set up Arenadata repo

    Whether or not to use the repository that is described in the field Arenadata repo url

    Arenadata repo url

    The repository that is required to install ADB

    Set up custom Arenadata enterprise repo

    Whether or not to use the repository that is described in the field Custom Arenadata enterprise repo

    Custom Arenadata enterprise repo

    Custom Arenadata Enterprise repository. If not filled in, the default repository will be used

    Set up monitoring repo

    Whether or not to use the repository that is described in the field Monitoring repo url

    Monitoring repo url

    The repository that is required to install monitoring
    Astra linux repositories
    Parameter Description

    Set up Arenadata repo

    Whether or not to use the repository that is described in the field Arenadata repo url

    Arenadata repo url

    The repository that is required to install ADB

    Set up custom Arenadata enterprise repo

    Whether or not to use the repository that is described in the field Custom Arenadata enterprise repo

    Custom Arenadata enterprise repo

    Custom Arenadata Enterprise repository. If not filled in, the default repository will be used

    Set up monitoring repo

    Whether or not to use the repository that is described in the field Monitoring repo url

    Monitoring repo url

    The repository that is required to install monitoring
    Centos 7 repositories
    Parameter Description

    Set up Arenadata repo

    Whether or not to use the repository that is described in the field Arenadata repo url

    Arenadata repo url

    The repository that is required to install ADB

    Set up custom Arenadata enterprise repo

    Whether or not to use the repository that is described in the field Custom Arenadata enterprise repo

    Custom Arenadata enterprise repo

    Custom Arenadata Enterprise repository. If not filled in, the default repository will be used

    Set up monitoring repo

    Whether or not to use the repository that is described in the field Monitoring repo url

    Monitoring repo url

    The repository that is required to install monitoring

    Set up Centos base repo

    Whether or not to use the repository that is described in the field Centos base repo url

    Centos base repo url

    Centos base repository

    Set up Centos updates repo

    Whether or not to use the repository that is described in the field Centos updates repo url

    Centos updates repo url

    Centos updates repository

    Set up Centos extras repo

    Whether or not to use the repository that is described in the field Centos extras repo url

    Centos extras repo url

    Centos extras repository

    Set up EPEL repo

    Whether or not to use the repository that is described in the field EPEL repo url

    EPEL repo url

    EPEL repository

  • Use existing docker — a flag that indicates whether to use the existing Docker during the installation of ADB services (e.g. ADB Control, ADBM, Monitoring, Enterprise Tools). If this flag is set, only containers will be deployed, while Docker and Docker Compose installation will be skipped. For more information on Docker requirements, see Software requirements.

    CAUTION

    Use all custom installations (Use existing docker, Use custom registry, Use custom JAVA_HOME for cluster) on your own risk.

  • Use custom registry — a switcher that determines whether to use a custom registry. When the switcher is activated, the following parameters are available.

    Parameter Description

    registry

    A custom registry URL prefix in the following form: <host>:<port> or <host>:<port>/<prefix_dir>

    Use self-signed certificate

    Whether or not to use a self-signed certificate

    Self-signed certificate

    A self-signed certificate text

  • Use custom JAVA_HOME for cluster — a switcher that indicates whether to use a custom Java path for ADB services (e.g. PXF, ADB Control, ADBM). Displayed if the Advanced flag is set. When the switcher is activated, the JAVA_HOME field becomes available. Enter a work Java path in that field. The selected path should contain а bin folder with a Java binary file, for example /usr/lib/jvm/java-11-openjdk-11.0.19.0.7-1.el7_9.x86_64/ or /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.221-2.6.18.0.x86_64/jre. If the JAVA_HOME value is empty, the default system path is used:

    • /usr/lib/jvm/jre-1.8.0-openjdk (RHEL/CentOS/AltLinux).

    • /usr/lib/jvm/bellsoft-java8-amd64/jre (Astra Linux).

    Installation will fail if there is no Java at the specified path. For more information on Java requirements, see Software requirements.

    TIP

    If you plan to use custom Java (such as Axiom), Java 11 is recommended for installation.

  • Parameter archiving — a switcher that indicates whether to export ADB settings according to the specified schedule. When the switcher is activated, the Parameter archiving job setting field becomes available. Enter a schedule for an export job in that field. The field value should be a valid cron expression. After you edit and save the Parameter archiving job setting value, run the cluster action Reconfigure parameter archiving.

    Each time a cron job is run, ADB settings are exported to the following directory:

    /home/gpadmin/arenadata_configs/settings/<timestamp>

    where <timestamp> is a timestamp of the export job launch in the YYYY-MM-DD_HH-mm-ss format.

    A job execution log is saved to the parameter_archiving.log file.

    Currently, the following settings are offloaded.

Service Exported parameters Relative path

ADB

GUC values for Master/Segment

./<YYYY-MM-DD_HH-mm-ss>_guc_config.json

Linux Greenplum-related parameters that are exported from /etc/sysctl.conf

./<YYYY-MM-DD_HH-mm-ss>_os_config.json

Resource group parameters. For more information, see Work with resource groups

./<YYYY-MM-DD_HH-mm-ss>_rg_config.json

ADB Control

Configuration parameters of ADB Control components

./adcc/*

ADBM

Configuration parameters of ADBM components

./adbm/*

PXF

PXF settings that are exported from:

  • /etc/pxf/conf/pxf-application.properties

  • /etc/pxf/conf/pxf-profiles.xml

  • $PXF_BASE/servers/*

./pxf_config/*
Cluster configuration window
Cluster configuration window
Found a mistake? Seleсt text and press Ctrl+Enter to report it