Software requirements

Contents

Overview

The software requirements for Arenadata DB installation are listed below:

  1. ADB supports the following operating systems:

    • Ubuntu 22.04 LTS (in ADB 6 starting with ADB 6.27.1.56).

    • Ubuntu 24.04 LTS (in ADB 6 starting with ADB 6.32.0).

    • ALT Linux 10.2 SP (for the Enterprise edition of ADB 6 starting with 6.29.1.1). The distribution release must be dated before November 2, 2026. PostGIS operability is not guaranteed on newer versions of the ALT Linux 10.2 SP distribution.

    • RED OS 7.3 Certified edition (for the Enterprise edition of ADB 6, starting with version 6.27.1.58) and RED OS 8.0 Certified edition (for the Enterprise edition of ADB 6, starting with version 6.31.0).

    • RHEL 9 (for the Enterprise edition of ADB 6, starting with version 6.31.0).

    • Astra Linux SE 1.7.6 Orel (for the Enterprise edition of ADB 6, starting with version 6.27.1.63).

    • Astra Linux SE 1.7.6 Voronezh (for the Enterprise edition of ADB 6, starting with version 6.29.0.3).

    • Astra Linux SE 1.8.4 Orel and Astra Linux SE 1.8.4 Voronezh (for the Enterprise edition of ADB 6, starting with version 6.30.0).

    • Astra Linux SE 1.8.6 Orel and Astra Linux SE 1.8.6 Voronezh (for the Enterprise edition of ADB 6, starting with version 6.32.0).

    • For all the operating systems, the system kernel must support cgroup v1.

  2. For the correct operation of ADB, configure cgroup v1 on all cluster hosts. You can do it manually in advance. Starting with version 6.26.0.53, ADB can also switch hosts to cgroup v1 automatically if you select the Reboot cluster servers after installation flag when installing and upgrading ADB. If the flag is not set and you haven’t switched to cgroup v1, ADB installation or upgrade will fail.

  3. ADB needs Java 17 for some services (for example, PXF). In all operating systems except Astra Linux, Java comes preinstalled. In Astra Linux, before ADB installation, you should install Java manually and fill in the Java path in the JAVA_HOME field when configuring the ADB cluster (this parameter is available in ADB 6 starting with ADB 6.25.2.52). This step is also necessary in other operating systems if you use Java 17 with a path different from the default one.

    The default Java paths for supported operating systems are listed below.

    • Ubuntu

    • ALT Linux

    • RED OS

    • RHEL

    /usr/lib/jvm/java-17-openjdk-amd64

    /usr/lib/jvm/jre-17

    /usr/lib/jvm/jre-17-openjdk

    /usr/lib/jvm/jre-17-openjdk

    IMPORTANT
    • If you plan to use custom Java (such as Axiom), Java 17 is required for installation.

    • For Astra Linux, the JAVA_HOME field is mandatory starting with ADB 6.27.1.58.

  4. Starting with ADB 6.31.0, the minimal ADCM version is 2.12.0.

  5. Starting with ADB 6.27.1.58, the minimal Yandex hostprovider version is 3.11.

  6. ADB requires the en_US.UTF-8 operating system locale on all cluster hosts. Yet you do not need to select this locale as default. This locale is present by default in all supported operating systems except Astra Linux. In the case of Astra Linux, the locale is automatically added during ADB installation. To view available locales, run the following command:

    $ localectl list-locales
  7. The recommended file system for ADB is XFS, which ensures optimal performance and stability.

  8. It is recommended to switch off any antivirus software before ADB installation and during the ADB operation process. In case of using antivirus, please contact your antivirus software vendor to find out the settings necessary to allow ADB.

  9. Only Latin characters and digits are allowed for ADB database objects. These characters are treated as reserved: ", &, ',   (space), (, ), ;, <, >, \, `, |. If such characters are present, Arenadata DB Backup Manager will not be able to back up/restore a database.

  10. During ADB installation, a bundle assigns the necessary permissions to the specific files and directories it creates, regardless of the umask value on cluster hosts.

  11. During ADB installation, the following changes are made at the operating system level. Do not change any of the objects listed below.

    • The following system files are modified:

      • /etc/fstab

      • /etc/hosts

      • /etc/hostname

      • /etc/chrony.conf

      • /etc/ssh/sshd_config

      • /etc/selinux/config

      • /etc/security/limits.conf

    • Some new files are created in the following folders:

      • /usr/lib/systemd/system/

      • /etc/cgconfig.d/

    • The SELinux service becomes disabled.

  12. The installation process creates a new file in the /var/spool/cron/ folder for ADB system user (by default, gpadmin). All technical accounts should be able to change that file as well (via crontab -e -u gpadmin).

  13. For online installation of ADB, all cluster hosts should have access to Arenadata repositories specified on the Configuration tab in the ADB cluster menu available via ADCM UI (see Arenadata repo url and Monitoring repo url fields). For offline installation, provide access to the host where the Enterprise Tools cluster is installed.

  14. For both online and offline installation, all cluster hosts should have access to the repositories that are listed below (or local mirrors should be created):

  15. ADB, like other analytical DBMS, is optimized to work with generic cores. Using the lowlatency cores may not provide optimal performance for tasks that are typical for analytical data processing. Due to this, for proper operation of ADB, it is recommended to use generic cores only.

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