Network requirements

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

  • All cluster servers should be connected to Interconnect networks.

  • All servers should have fully qualified domain names (FQDN) and the ability to communicate with each other at required speeds.

  • The IP address of each server should be known.

  • Ping access to any server (ICMP) should be provided.

  • For online ADPG installation, access to Arenadata Cluster Manager deployed on a dedicated server is required. See the Install ADCM article for details on how to install Arenadata Cluster Manager.

  • For offline ADPG installation, access to Arenadata Enterprise Tools deployed on a dedicated server is required. The Install Enterprise Tools cluster section contains instructions on how to install Arenadata Enterprise Tools.

  • The ports listed below should be open on hosts where you install the specified service.

  • ADPG

  • Enterprise Tools

  • ADCM

Service Port Purpose

Common

11203

Port on cluster hosts to access system metrics in the Prometheus format

ADPG

5432

The default port that the ADPG service (PostgreSQL) listens on

15432

The default port that PgBouncer listens on

8008

Patroni REST API port — the port on a host with the ADPG service to retrieve Patroni metrics in the Prometheus format

9187

Port on a host with the ADPG service to retrieve PostgreSQL metrics in the Prometheus format

9188

Port on a host with the ADPG service to retrieve connection pooler (PgBouncer) metrics in the Prometheus format

9854

Port on a host with the ADPG service to retrieve PgBackRest metrics in the Prometheus format

Balancer

6432

Port on a host with the HAProxy component for write transactions

6433

Port on a host with the HAProxy component for read only transactions

7000

Port on which a web page with a HAProxy statistics report is available

16432

Port, all connections to which are transferred to a PgBouncer instance of an ADPG leader node

16433

Port, all connections to which are transferred to PgBouncer instances of ADPG replica nodes

8405

Port on a host with the Balancer service to retrieve HAProxy metrics in the Prometheus format

Etcd

2380

Port for peer communication

2379

Port for client requests — port on a host with the Etcd service to retrieve PgBackRest metrics in the Prometheus format

Monitoring

11200

Port to access the Prometheus web interface

11210

Port to access the Grafana web interface

Port Purpose

443

TCP port used by Arenadata Enterprise Tools (Docker Registry service)

81

TCP port used by Arenadata Enterprise Tools (access to the official repositories for offline installation)

Port Purpose

8000

TCP port to send statuses of cluster components to ADCM

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