Конференция Arenadata
Новое время — новый Greenplum
Мы приглашаем вас принять участие в конференции, посвященной будущему Open-Source Greenplum 19 сентября в 18:00:00 UTC +3. Встреча будет проходить в гибридном формате — и офлайн, и онлайн. Онлайн-трансляция будет доступна для всех желающих.
Внезапное закрытие Greenplum его владельцем — компанией Broadcom - стало неприятным сюрпризом для всех, кто использует или планирует начать использовать решения на базе этой технологии. Многие ожидают выхода стабильной версии Greenplum 7 и надеются на её дальнейшее активное развитие.
Arenadata не могла допустить, чтобы разрабатываемый годами Open-Source проект Greenplum прекратил своё существование, поэтому 19 сентября мы представим наш ответ на данное решение Broadcom, а участники сообщества получат исчерпывающие разъяснения на все вопросы о дальнейшей судьбе этой технологии.

На конференции вас ждёт обсуждение следующих тем:

  • План возрождения Greenplum;
  • Дорожная карта;
  • Экспертное обсуждение и консультации.
Осталось до события

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. The Configuration tab includes the following sections: Primary configuration, Configuration groups, Ansible settings.

  3. Fill in all necessary parameters on the selected tab and click Save.

Primary configuration

The Configuration → Primary configuration tab allows you to configure the general cluster settings.

Available 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, Ubuntu). 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
    Ubuntu 22.04 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 in the following form: <host>:<port>

    prefix

    An optional subdirectory name that will be added to the custom registry URL: <registry>/<prefix>

    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 Show 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/. If the JAVA_HOME value is empty, the default system path is used:

    • /usr/lib/jvm/jre-11-openjdk (for all operating systems)

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

    IMPORTANT

    If you plan to use custom Java (such as Axiom), Java 11 is required 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/*

  • Timeout to unlock package manager — parameters of this section are intended to set the timeout of the DNF software package manager unlocking wait. In Ubuntu, after the host reboot, automatic update starts, which locks DNF.

    Name Description Default

    retries

    The maximum number of retries

    3

    delay

    The time delay between retries (in seconds)

    10

  • Vault integration — a switcher that indicates whether to use HashiCorp Vault to store secrets of ADB services. When the switcher is activated, the following parameters become available.

    Name Description Default

    Address of the Vault server

    The Vault server address (e.g. 192.168.1.120 or vault.domain.com)

     — 

    Port of the Vault server

    The Vault server port. Should be specified if the service is published on a port other than HTTPS (443)

    443

    Internal CA certificate in PEM format (optional)

    The internal CA certificate in PEM format that signed the Vault server’s certificate

     — 

    Vault namespace (optional)

    The Vault namespace

     — 

    Writer authentication method for the Vault server

    The authentication method that is used to connect to the Vault server with write access.

    Possible values:

    • token

    • approle

    approle

    Writer Vault token

    The application token that is used to connect to the Vault server with write access. Required only if the Writer authentication method for the Vault server parameter is set to token

     — 

    Writer Vault role ID

    The role identifier provided for applications to connect to the Vault server with write access. Required only if the Writer authentication method for the Vault server parameter is set to approle

     — 

    Writer Vault secret ID

    The secret identifier associated with the Writer Vault role ID role that is used by applications to connect to the Vault server with write access. Required only if the Writer authentication method for the Vault server parameter is set to approle

     — 

    Reader authentication method for the Vault server

    The authentication method that is used to connect to the Vault server with read access.

    Possible values:

    • token

    • approle

    approle

    Reader Vault token

    The application token that is used to connect to the Vault server with read access. Required only if the Reader authentication method for the Vault server parameter is set to token

     — 

    Reader Vault role ID

    The role identifier provided for applications to connect to the Vault server with read access. Required only if the Reader authentication method for the Vault server parameter is set to approle

     — 

    Reader Vault secret ID

    The secret identifier associated with the Reader Vault role ID role that is used by applications to connect to the Vault server with read access. Required only if the Reader authentication method for the Vault server parameter is set to approle

     — 

    Mount point for ADB cluster secrets

    A mount point that is accessible for read/write operations with the provided ADB cluster authentication parameters. Each service will store secrets on the Vault server at the following path: <Mount point for ADB cluster secrets>/adb/<cluster_name>/service/<service_name>/<component>

     — 
IMPORTANT

  • Before editing Vault integration parameters, ensure that Vault is installed and configured.

  • Each time you edit and save parameters in the Vault integration section, run the cluster action Reconfigure Vault integration.

  • Currently, Vault can be used to store authentication parameters of ADB Control and ADBM.
Cluster configuration window
Cluster configuration window

Configuration groups

The Configuration → Configuration groups tab is designed to set cluster configuration groups.

Ansible settings

The Configuration → Ansible settings tab allows you to set Ansible configuration options at the cluster level. The tab is available starting with ADCM 2.2.0.

Ansible settings
Name Description Default

forks

The number of parallel processes to spawn when communicating with remote hosts

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