Configuration parameters
This article describes the parameters that can be configured for ADB services via ADCM. To read about the configuring process, refer to the relevant articles: Online installation, Offline installation.
NOTE
Some of the parameters become visible in the ADCM UI after the Show advanced flag being set.
|
ADB
Parameter | Description | Default value |
---|---|---|
Name of default database |
A name of the database created by default. This database is maintained by crontab scripts (garbage collection, transaction wraparound, etc.) |
adb |
Use segment mirroring |
Enables synchronous replication for primary data segments, i.e. adds mirror segments to the cluster. As a result, mirror segments provide higher availability for the stored data, but require twice more space. When the cluster has enough hosts, it uses spread mirroring policy, otherwise — group mirroring policy |
true |
ADB MADlib Extension |
Whether or not to install the ADB MADlib Extension. MADlib is an open-source library for scalable in-database analytics that provides data-parallel implementations of mathematical, statistical, and machine-learning methods for structured and unstructured data. It provides a suite of SQL-based algorithms for machine learning, data mining, and statistics, that run at scale within a database engine with no need for transferring data between ADB and other tools |
false |
ADB PostGIS Extension |
Whether or not to install the PostGIS Extension. PostGIS is a spatial database extension for PostgreSQL that allows GIS (Geographic Information Systems) objects to be stored in the database. The PostGIS extension includes support for GiST-based R-Tree spatial indexes and functions for analysis and processing of GIS objects |
false |
ADB Auto Core Dump Service |
Whether or not to install Auto Core Dump Service — a plugin that enables core dump files for ADB processes. This feature is useful for debugging purposes. If enabled, the system collects core dumps and saves them in the following directory: /var/lib/systemd/coredump/. When the maximum storage size is reached (1 GB), old files will be deleted. The parameter is available in ADB 6 starting with 6.21.1.36 |
false |
Diskquota Extension |
Whether or not to install the Diskquota Extension. The Diskquota module allows Arenadata DB administrators to limit the amount of the disk space used by schemas or roles in the database |
false |
PL/Python3u Extension |
Whether or not to install the PL/Python3u Extension |
false |
Parameter | Description | Default value |
---|---|---|
Number of segments per host |
A number of primary segments on each Segment host. If the parameter is not set, then |
(<Number of CPU cores>) / 2 |
Segment host data directories |
Directories that are used to store data on Segment hosts. The |
/data1 |
Use nobarrier for segments |
Whether or not to use the |
false |
Masters host data directory |
Directories that are used to store data on Master and Standby Master hosts |
/data1 |
Mount master storage device for data |
Whether or not to mount block storage devices to data directories on Master and Standby Master hosts. If no block storage devices are listed in the |
false |
Master server storage device |
Master storage devices, e.g. |
— |
Use nobarrier for master |
Whether or not to use the |
false |
Arenadata configs directory name |
A name of the folder that contains Arenadata configuration files. It is located in the system user home directory |
arenadata_configs |
Sysctl parameters |
Linux kernel parameters that are needed for ADB |
— |
System user GID |
A unique identifier of the group that the system user belongs to. A system user should be created with the same UID and GID across all cluster servers in order to reduce problems with access to the common network storages, containing ADB backup files |
2042 |
System user name |
A system user name for ADB |
gpadmin |
System user UID |
A unique identifier of the system user. A system user should be created with the same UID and GID across all cluster servers in order to reduce problems with access to the common network storages, containing ADB backup files |
2042 |
Disable firewall |
Whether or not to disable firewalld on the cluster hosts |
true |
Edit /etc/hosts |
Whether or not to edit the /etc/hosts file during ADB installation to provide short host names instead of FQDN for the correct ADB work |
true |
Amount of shared memory |
The amount of shared memory allocated for query metrics (in KB). The maximum size is |
5120 |
Maximum scan node’s instrumentations |
The maximum number of scan node’s instrumentations per query (in shmem). Restart ADB to apply changes |
300 |
Parameter | Description | Default value |
---|---|---|
Interconnect type |
An interconnect type that should be used. Possible values:
|
udpifc |
ic-proxy auto-discovery |
Whether to use automatic proxy list generation during ic-proxy interconnect configuration. A port shift is defined in the ic-proxy port delta field (by default, |
true |
ic-proxy port delta |
Defines an integer value that is used to increase/decrease the proxy port value relative to the port of the associated postmaster backend. Applies only in conjunction with ic-proxy auto-discovery set to Allowed values: Please do not use |
2000 |
Run ic-proxy check |
Whether to run an interconnect test |
false |
Parameter | Description | Default value |
---|---|---|
Cluster network |
A subnet that is used for cluster nodes interconnection. Requires the |
— |
Parameter | Description | Default value |
---|---|---|
ADB ident server |
Whether to install the Ident server |
false |
Type of ident server |
A type of the Ident server. Currently, only the oidentd type is supported |
oidentd |
Default deny policy for ident server |
Whether to deny access by default for all users for which no explicit rules have been defined in the configuration file of the Ident server (/etc/oidentd.conf) |
true |
Parameter | Description | Default value |
---|---|---|
ADB GPperfmon Extension |
Whether to install the ADB GPperfmon extension. GPperfmon is a built-in activity monitor that populates tables in the |
true |
Authentication type |
An authentication type that should be defined in the pg_hba.conf file for the
To use the |
md5 |
Parameter | Description | Default value |
---|---|---|
Crontab maintenance scripts |
Crontab maintenance scripts of the ADB system user |
— |
Delete old maintenane script logs |
A number of days after which maintenance script logs should be deleted |
30 |
Parameter | Description | Default value |
---|---|---|
SSL |
Whether to use SSL certificates |
false |
SSL Ciphers |
SSL ciphers |
["HIGH","MEDIUM","+3DES","!aNULL"] |
Server certificate |
Server certificate contents in the CRT format (*.crt file) |
— |
Server private key: |
Server private key contents (*.key file) |
— |
Root certicate |
Root certificate (Certificate Authority, CA) contents in the CRT format (*.crt file) |
— |
Certificate revocation list |
Certificates revoked by certificate authorities |
— |
Custom ssl pg_hba section |
Th custom part of the pg_hba file (with SSL settings) |
— |
Parameter | Description | Default value |
---|---|---|
UI LDAP authentication |
Whether or not to use LDAP authentication |
false |
Type |
A type of the LDAP server. Possible values:
|
MSAD |
URI |
A URI for connecting to the LDAP server in the following format: |
— |
Users baseDN |
A limitation of the search scope of objects in the LDAP directory that is used in user search requests |
— |
Groups baseDN |
A limitation of the search scope of objects in the LDAP directory that is used in group search requests |
— |
Users filter |
An LDAP filter that is used to search users. Should be specified according to the RFC 2254 |
(&(|(objectClass=person)(objectClass=inetOrgPerson))(cn=*)) |
Groups filter |
An LDAP filter that is used to search groups. Should be specified according to the RFC 2254 |
(&(|(objectClass=group)(objectClass=groupofnames)(objectClass=groupOfUniqueNames))(cn=*)) |
SA Login |
A user name that is used for service requests to the LDAP server |
— |
Password |
A user password that is used for service requests to the LDAP server |
— |
Lowercase login |
Whether or not to convert user names to lowercase |
false |
Lowercase group |
Whether or not to convert group names to lowercase |
false |
Sync interval |
A cron expression that defines how often synchronization of ADB users and groups with an LDAP server should be performed. The pg-ldap-sync utility, which comes with the ADB bundle, is used for synchronization |
0 * * * * |
Parameter | Description | Default value |
---|---|---|
Custom pg_hba section |
A custom part of the pg_hba.conf file |
— |
ADB Control
Parameter | Description | Default value |
---|---|---|
External ADB Control server parameters |
Whether or not to use an external ADB Control server |
false |
ADB Control IP-address |
An external ADB Control IP address. The property becomes available after setting the |
— |
External ADB Control port |
An external ADB Control port. The property becomes available after setting the |
81 |
Parameter | Description | Default value |
---|---|---|
ADB user name |
A user name that is used by ADB Control for connecting to ADB. Such access is required to obtain information about the cluster topology and to cancel requests initiated by users |
adcc |
Service password |
The service API user password for interaction between ADB Control and ADCM. It is recommended to change the default value |
— |
Servername |
A server name for connecting to the ADB Control via HTTP |
— |
Listening port |
A port on which ADB Control UI is available via HTTP |
81 |
Xmx ram parameter |
A maximum Java heap size for the UI component |
8 |
Log level |
A logs level that is used by the UI component.
Possible values are |
INFO |
Parameter | Description | Default value |
---|---|---|
HTTPS parameters enable |
Wether or not to enable ADB Control UI via HTTPS |
false |
Server certificate |
Server certificate contents in the CRT format (*.crt file) |
— |
Server private key |
Server private key contents (*.key file) |
— |
Verify system endpoints' certificates |
A flag that indicates whether to verify certificates of system endpoints. When using the Verify system endpoints' certificates option in the ADB Control configuration with self-signed certificates, ensure that you added the root and intermediate CA certificates to the OS trusted root certificate stores. In order to use the Verify system endpoints' certificates option with your own certificates, for proper verification, add the ADB Control IP address to the |
false |
Server JKS keystore path |
A path to the keystore file in the JKS format for the ADB Control server part. For example, /opt/adcc/ssl/keystore.jks |
— |
Server JKS keystore password |
A password that is used for connecting to |
— |
Server JKS truststore path |
A path to the truststore file in the JKS format for the ADB Control server part. For example, /opt/adcc/ssl/truststore.jks |
— |
Server JKS truststore password |
A password that is used for connecting to |
— |
Client JKS keystore path |
A path to the keystore file in the JKS format for the ADB Control client part (ADB Control/ADBM agents). For example, /opt/ssl/keystore.jks |
— |
Client JKS keystore password |
A password that is used for connecting to |
— |
Client JKS truststore path |
A path to the truststore file in the JKS format for the ADB Control client part (ADB Control/ADBM agents). For example, /opt/ssl/truststore.jks |
— |
Client JKS truststore password |
A password that is used for connecting to |
— |
Parameter | Description | Default value |
---|---|---|
UI LDAP authentication |
Whether or not to use LDAP authentication |
false |
LDAP type |
A type of the LDAP server. Possible values:
|
MSAD |
LDAP URI |
A URI for connecting to the LDAP server. Requires the following format: |
— |
Internal CA certificate in PEM format (optional) |
The internal CA certificate or certificate chain in PEM format that signed the LDAP server certificate |
— |
Users baseDN |
A limitation of the search scope of objects in the LDAP directory that is used in users search requests |
— |
Groups baseDN |
A limitation of the search scope of objects in the LDAP directory that is used in groups search requests |
— |
Users OUs |
A list of |
— |
Groups OUs |
A list of |
— |
Group |
A group name that is used for service requests to the LDAP server |
— |
Login |
A user name that is used for service requests to the LDAP server |
— |
Password |
A user password that is used for service requests to the LDAP server |
— |
Size limit |
A maximum number of records that can be returned by the LDAP server |
1000 |
Lowercase login |
Whether or not to convert user names to lowercase |
false |
Parameter | Description | Default value |
---|---|---|
Xmx ram parameter |
A maximum Java heap size for the backend component |
8 |
Log level |
A logs level that is used by the backend component.
Possible values are |
INFO |
Parameter | Description | Default value |
---|---|---|
Xmx ram parameter |
A maximum Java heap size for the registry component |
2 |
Log level |
A logs level that is used by the registry component.
Possible values are |
INFO |
Parameter | Description | Default value |
---|---|---|
Database name |
A name of the PostgreSQL database where ADB Control stores data (Query DB) |
adcc |
Username |
A user name that is used for connecting to the PostgreSQL database |
postgres |
Password |
A user password that is used for connecting to the PostgreSQL database |
— |
Listening port |
A listening port for the PostgreSQL database |
5433 |
Data dir |
A full path to the directory where ADB Control stores PostgreSQL data. ADB Control uses the default Docker volume directory unless otherwise specified |
— |
CAUTION
The Data dir directory should be empty before database initialization during ADB Control installation. |
Parameter | Description | Default value |
---|---|---|
External database parameters |
Whether or not to use an external PostgreSQL database as Query DB for ADB Control |
false |
Server ip |
An IP address of the server where the external PostgreSQL database is stored |
— |
External database port |
A listening port of the server where the external PostgreSQL database is stored |
5432 |
Database name |
A name of the external PostgreSQL database |
adcc |
Username |
A user name that is used for connecting to the external PostgreSQL database |
postgres |
Password |
A user password that is used for connecting to the external PostgreSQL database |
— |
Parameter | Description | Default value |
---|---|---|
Migration completion timeout |
A migration completion timeout (in minutes) |
5 |
Parameter | Description | Default value |
---|---|---|
Data dir |
A full path to the directory where ADB Control stores ClickHouse data. ADB Control uses the default Docker volume directory unless otherwise specified |
— |
Database name |
A name of the ClickHouse database that is used as Metrics DB in ADB Control |
adcc |
Username |
A user name that is used for connecting to the ClickHouse database |
default |
Password |
A user password that is used for connecting to the ClickHouse database |
— |
Parameter | Description | Default value |
---|---|---|
External ADQM parameters |
Whether or not to use an external ClickHouse database as Metrics DB for ADB Control |
false |
ADQM address and port [ip_address:port] |
An address of the server where the external ClickHouse database is stored. Starting with ADB Control 4.8.8, you can use clustered ClickHouse as an external database for ADB Control installation (in addition to a standalone node). To do this:
|
— |
Database name |
A name of the external ClickHouse database |
adcc |
Username |
A user name that is used for connecting to the external ClickHouse database |
— |
Password |
A user password that is used for connecting to the external ClickHouse database |
— |
Parameter | Description | Default value |
---|---|---|
Xmx ram parameter |
A maximum Java heap size for ADB Control agents |
2 |
Log level |
A logs level that is used by ADB Control agents.
Possible values are |
INFO |
Servers list update timeout |
A timeout between refreshing information about available ADB Control Backend Servers instances (in ms) |
5000 |
Parameter | Description | Default value |
---|---|---|
Xmx ram parameter |
A maximum Java heap size for ADB Control scheduler |
2 |
Log level |
A logs level that is used by ADB Control scheduler.
Possible values are |
INFO |
Parameter | Description | Default value |
---|---|---|
Dedicated network |
A subnet that is used for ADB Control/ADBM interconnection. Requires the If the ADB Control IP address is used in the |
— |
Parameter | Description | Default value |
---|---|---|
Backend app parameters |
Application parameters of the ADB Control backend |
— |
Backend logback parameters |
Logback parameters of the ADB Control backend |
— |
Registry app parameters |
Application parameters of the ADB Control registry |
— |
Registry logback parameters |
Logback parameters of the ADB Control registry |
— |
UI server app parameters |
Application parameters of the ADB Control UI |
— |
UI server logback parameters |
Logback parameters of the ADB Control UI |
— |
Scheduler app parameters |
Application parameters of the ADB Control scheduler |
— |
Scheduler logback parameters |
Logback parameters of the ADB Control scheduler |
— |
Migration app parameters |
Properties of the migration application |
— |
ADB Control agent properties |
Properties of the ADB Control agent |
— |
ADB Control agent logback parameters |
Logback parameters of the ADB Control agent |
— |
ADB Control agent override parameters |
Override parameters of the ADB Control agent |
— |
ADB Control agent service config parameters |
Service configuration parameters of the ADB Control agent |
— |
ADBM
Parameter | Description | Default value |
---|---|---|
Xmx ram parameter |
A maximum Java heap size for the ADBM backend |
8 |
Log level |
A logs level that is used by the ADBM backend.
Possible values are |
INFO |
Parameter | Description | Default value |
---|---|---|
Xmx ram parameter |
A maximum Java heap size for the ADBM agent |
2 |
Log level |
A logs level that is used by the ADBM agent.
Possible values are |
INFO |
Parameter | Description | Default value |
---|---|---|
External database parameters |
Whether or not to use an external PostgreSQL database for ADBM |
false |
Server ip |
An IP address of the server where the external database is stored |
— |
External database port |
A listening port of the server where the external database is stored |
5432 |
Database name |
A name of the external database |
adbm |
Username |
A user name that is used for connecting to the external database |
postgres |
Password |
A user password that is used for connecting to the external database |
— |
Parameter | Description | Default value |
---|---|---|
Migration completion timeout |
A migration completion timeout (in minutes) |
3 |
Xmx ram parameter GB |
The maximum memory pool allocated for a Java Virtual Machine (JVM) in GB |
1 |
Parameter | Description | Default value |
---|---|---|
Backend app parameters |
Application parameters of the ADBM backend |
— |
Backend logback parameters |
Logback parameters of the ADBM backend |
— |
Backend auth properties |
Authorization properties of the ADBM backend |
— |
ADBM agent properties |
Properties of the ADBM agent |
— |
ADBM agent logback parameters |
Logback parameters of the ADBM agent |
— |
ADBM agent override parameters |
Override parameters of the ADBM agent |
— |
ADBM agent service config parameters |
Service configuration parameters of the ADBM agent |
— |
ADBM CLI config parameters |
Configuration parameters of the ADBM CLI |
— |
ADBM CLI log parameters |
Logging parameters of the ADBM CLI |
— |
ADBM CLI auth properties |
Authorization properties of the ADBM CLI |
— |
Chrony
Parameter | Description | Default value |
---|---|---|
NTP servers |
Addresses of valid NTP servers. For example, |
— |
Monitoring Clients
Parameter | Description | Default value |
---|---|---|
Protocol |
A transport protocol for sending metrics to the monitoring cluster. Possible values are |
TCP |
Enable echo ADB-specific metrics |
Whether or not to echo ADB-specific metrics to the output of the /home/gpadmin/arenadata_configs/arenadata_segments_monitor.sh monitoring script |
false |
Check adb monitoring |
Whether or not to check if monitoring agents are installed on the ADB service hosts |
true |
PXF
Parameter | Description | Default value |
---|---|---|
Use custom JAVA_HOME |
Whether or not to use a custom JAVA_HOME path |
false |
JAVA_HOME |
A custom JAVA_HOME path. Should lead to the working JAVA. The property becomes available after setting the
For CentOS and Astra Linux, the JAVA_HOME field is mandatory starting with ADB 6.27.1.58 |
— |
PXF_JVM_OPTS |
Sets |
-Xmx2g -Xms1g |
PXF log4j properties |
log4j properties for PXF |
— |
Use custom PXF_BASE |
Whether or not to use a custom PXF_BASE path |
false |
PXF_BASE |
A custom PXF_BASE path for PXF installation. The property becomes available after setting the |
/var/lib/pxf |
Encryption |
Whether or not to use encryption |
false |
Keystore file |
An absolute path to the JKS keystore file. For example, |
— |
Keystore password |
A JKS keystore password |
— |
Encryption key alias |
An encryption key alias. Do not enter a private key in this field |
— |