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.
-
IP address of each server should be known.
-
Ping access to any server (ICMP) should be provided.
-
For online installation of ADQM, 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 installation of ADQM, 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.
-
Ports below should be open on servers where you install the cluster.
|
NOTE
Each port refers to the server where a specific service is installed.
|
| Service | Port | Purpose |
|---|---|---|
Common |
22 |
Port for connection to SSH provider |
2015 |
TCP port to send metrics to the ADM monitoring cluster (deprecated) |
|
2016 |
UDP port to send metrics to the ADM monitoring cluster (deprecated) |
|
ClickHouse |
8123 |
HTTP port for client or proxy connections |
8443 |
Port for secure client connections via the HTTPS interface (see Enable SSL encryption for details) |
|
9000 |
Port for client connections via the Native (TCP) protocol. This port is also used for interserver interaction when performing distributed queries |
|
9440 |
TCP port for secure communication with clients and interserver communication for distributed queries |
|
9009 |
Port for communication between replicas |
|
9100 |
Port for client connections via gRPC |
|
9019 |
JDBC Bridge port |
|
9363 |
Port to listen for ClickHouse metrics in the Prometheus format |
|
ZooKeeper |
2181 |
Service access port |
2888 3888 |
Server-to-server сommunication ports for quorum components |
|
2281 |
Port for secure client connections |
|
9020 |
Port to listen for ZooKeeper metrics in the Prometheus format |
|
ClickHouse Keeper |
2129 |
TCP port for client connections |
9444 |
Recommended port for RAFT connections (also used for secure сommunications if |
|
9281 |
Recommended port for secure SSL-encrypted interaction |
|
9010 |
Port to listen for ClickHouse Keeper metrics in the Prometheus format |
|
Monitoring |
11210 |
Port to access the Grafana web interface |
11203 |
Port to access ADQM host system metrics in the Prometheus format |
|
Сhproxy |
9090 |
HTTP port for client connections |
8543 |
HTTPS port for client connections |
| Port | Purpose |
|---|---|
3000 |
HTTP port to access the Grafana web interface. You can change the default value when installing the monitoring cluster on the configuration page of the Grafana service in the ip_and_ports section |
80 |
TCP port to access the Graphite web interface. You can change the default value when installing the monitoring cluster on the configuration page of the Graphite service in the ip_and_ports section |
| 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 |