Software requirements

ADB supports the following operating systems:

If you use ClickHouse or PostgreSQL as external storage systems for ADB Control/ADBM (see Metrics DB and Query DB in Arenadata DB Control overview), the minimal required versions of these databases are:

ADB needs Java 17 for some services (e.g. PXF, ADB Control, ADBM). In all operating systems except Astra Linux, no additional Java installation is needed since Java comes with the main operating system repository. 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.

Starting with ADB 6.27.1.63, the minimal ADCM version is 2.6.0.

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

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

The recommended file system for ADB is XFS, which ensures optimal performance and stability.

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.

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.

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.

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

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

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.

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):

For the correct operation of ADB under Astra Linux and Ubuntu, it is necessary to configure cgroup v1. There are two options for switching hosts to cgroup v1:

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.

You should also consider version compatibility.