Network requirements

Daria Barysheva

Overview

The network requirements for Arenadata DB installation are listed below:

  • One or more dedicated and separate peer-to-peer interconnect networks are required for internal cluster communication.

  • All cluster hosts should be connected to interconnect networks.

  • All cluster hosts should have IP addresses and the ability to communicate with each other at required speeds.

  • ping access to any cluster host (ICMP) should be provided.

  • The jumbo frame MTU = 9000 should be specified in interconnect networks to allow packets formed by ADB (gp_max_packet_size + overhead) to fit into these frames.

  • The Ethernet speed 1 Gbps or more should be provided (the standard value is 10 Gbps).

  • There should be no firewall or other software that blocks or slows down the traffic (firewalld, iptables, ufw, etc.). If firewall software is not deactivated, you should configure your software to allow required communication between ADB hosts. For more information, see Greenplum documentation.

  • From the outside, the ADB cluster should be available on the following ports:

    • 22 — SSH;

    • 5432 — income PostgreSQL interface.

  • To access NTP (Network Time Protocol) servers, the master host should be allowed to connect to it (by default, via the 123/udp port).

  • To send cluster component statuses to Arenadata Cluster Manager (ADCM), ADB hosts should be allowed to connect to it (by default, via the 8000/tcp port). See the Install ADCM article for details on how to install ADCM.

  • If monitoring is used, the ports listed in Monitoring service ports should be open on the host where the monitoring service is installed. The monitoring service installation is described in Install monitoring.

  • For offline installation of ADB, access to Arenadata Enterprise Tools repositories deployed on a dedicated host is required (by default, via the 81/tcp port). The Install Enterprise Tools cluster section contains instructions on how to install Arenadata Enterprise Tools.

  • All ports that are listed below should be open on the respective hosts. If you use firewall, add ports to the exception list.

Ports

ADB ports

  • Master/standby

  • All cluster hosts

  • Cluster or external hosts

  • ADQM/ClickHouse host

Service Port Protocol Note

ADB

5432

TCP

SQL client connection port on the ADB master host. Supports clients using the PostgreSQL libpq API. Configurable

Standby master replicator

1025-65535

TCP

Ports for replication the master log to the standby master
Service Port Protocol Note

Secure shell (SSH): gpssh, gpscp, gpssh-exkeys, gppkg

22

SSH

Many Greenplum utilities use Secure Copy Protocol (SCP) and Secure Shell (SSH) to manage a cluster and transfer files between hosts

Interconnect

10000-65535

UDP

The interconnect transports database tuples between ADB segments during query execution (for exact ports refer to the gp_segment_configuration system table)

Gpperfmon agents

8888

TCP

Connection port for gpperfmon agents (gpmmon and gpsmon) executing on ADB hosts. Configure by setting the gpperfmon_port parameter in postgresql.conf on master and segment hosts

PXF

5888

TCP

The PXF Java service runs on the 5888 port on each ADB segment host

gpbackup

25

587

TCP

 — 
Service Port Protocol Note

gpfdist

8080

HTTP

The gpfdist file serving utility can run on ADB hosts or external hosts. You can specify the port range with the -p (start port) and -P (end port) options when starting the server. The 8080 value is used as the start port by default

gpload

8000-9000

HTTPS

The gpload utility runs one or more instances of gpfdist with ports or port ranges specified in the configuration file. The 8000-9000 range is used by default and can be changed
Service Port Protocol Note

ADB ClickHouse Connector

8123

HTTP

All ADB nodes should have access to the 8123 HTTP port on all ADQM/ClickHouse nodes through which you plan to load data

If you use ADB to ADB Connector, ensure that TCP ports that are used in connection are allowed on remote ADB cluster hosts (master host, segment hosts, standby host). You can obtain the list of these ports using the following query on remote ADB cluster:

SELECT port FROM gp_segment_configuration;

Add exceptions for the ports from the command output in case of using firewall.

ADBC agents ports

Service Port Protocol Note

Agent

6581

TCP

Port for the utility service that is used to manage GUCs which are changed via ADB Control

Agent

5701

TCP

Port that is used as a part of the Hazelcast (distributed cache) cluster node address. The port should be opened on every ADB cluster host (with the ADB Control agent) since it is used for communication between Hazelcast cluster nodes

Agent

From 36001 to 36001 + <number of ADB hosts> - 1

TCP

Range of allowed outbound ports for connections to other members or clients within a Hazelcast cluster. The ports should be opened on every ADB cluster host with the ADB Control agent

ADBM agents ports

Service Port Protocol Note

Agent

6571

TCP

The port through which gRPC calls from ADBM to agents come

Arenadata Enterprise Tools ports

Port Protocol Note

81

TCP

Port that is used to access repositories during offline installation

Monitoring service ports

Port Protocol Note

11210

HTTP

Port to access the Grafana web interface. You can change the default value in the Monitoring service configuration parameters in the Grafana settings section

11200

HTTP

Port to access the Prometheus web interface. You can change the default value in the Monitoring service configuration parameters in the Prometheus settings section

11203

HTTP

Port to access Node Exporter. You can change the default value in the Monitoring service configuration parameters in the Node Exporter settings section

9080

HTTP

Port to access the Greengage Exporter. You can change the default value in the Monitoring service configuration parameters in the Greengage Exporter settings section

9256

HTTP

Port to access Process Exporter. You can change the default value in the Monitoring service configuration parameters in the Process exporter settings section
Found a mistake? Seleсt text and press Ctrl+Enter to report it