Configure a cluster
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:
-
Select a cluster on the Clusters page. To do this, click a cluster name in the Name column.
Select a cluster -
Open the Configuration tab on the cluster page. The Configuration tab includes the following sections: Primary configuration, Configuration groups, Ansible settings.
-
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.
Cluster configuration parameters are listed below:
-
Reliability control — parameters of this section are intended to set the timeout of the DNF software package manager unlocking wait. Displayed if the Show advanced switch is activated. In Ubuntu, after the host reboot, automatic update starts, which locks DNF.
Name Description Default retries
The maximum number of retries
80
delay
The time delay between retries (in seconds)
30
timeout
Timeout for network ports checks (in seconds)
7200
-
Paths to the repositories that are used during the installation process depending on the cluster operating system (CentOS, Red Hat, Ubuntu, ALT Linux 8, or Astra Linux). Only the marked repositories are registered on the cluster servers.
RepositoriesParameter Description monitoring
YUM repository for installing monitoring
zookeeper_repo
Arenadata Zookeeper YUM repository
ADS
ADS YUM epository
ranger plugins
repository for installing Ranger client (only for Enterprise version)
-
Precheck packages — enables package availability check before installation.
-
Docker registry url — specifies the location of Arenadata Docker Registry. Displayed if the Show advanced switch is activated.
-
Znode path for cluster in Zookeeper service — Znode path for the ADS cluster in the Zookeeper service. Displayed if the Show advanced switch is activated.
-
BASIC Authentication — configuration for BASIC authentication.
For a description of enabling authentication, see the article Basic authentication.
-
SASL_PLAINTEXT Authentication — configuration for SASL PLAINTEXT authentication.
For a description of enabling authentication, see the article SASL PLAINTEXT.
-
Kerberos — configuration for Kerberos authentication.
The description of enabling authentication is given in the articles:
-
java.io.tmpdir — a Java system property that determines where the JVM writes temporary files.
-
Custom JDK settings — a switch that indicates whether to use a custom Java path for ADS services. When the switch 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/jre-openjdk/. If the JAVA_HOME value is empty, the default system path is used: /usr/lib/jvm/java-1.17.0-openjdk-amd64/ (for all operating systems except Centos, RedHat, and AstraLinux).

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.
Name | Description | Default |
---|---|---|
forks |
The number of parallel processes to spawn when communicating with remote hosts |
5 |