Network requirements
-
One or more dedicated peer-to-peer Interconnect networks are required for internal cluster communication.
-
All cluster servers must be connected to Interconnect networks.
-
All servers must have a fully qualified domain name (FQDN) and the ability to communicate with each other at required speeds.
-
The IP address of each server must be known.
-
Ping access to any servers (ICMP) must be provided.
-
In the case of installation with Internet access, access is required to the Arenadata Cluster Manager deployed on a dedicated server. Installation of Arenadata Cluster Manager is described in the article Install ADCM.
-
In the case of installation without Internet access (offline), access is required to the Arenadata Enterprise Tools deployed on a dedicated server. Installation of Enterprise Tools is described in the section Install Enterprise Tools cluster.
-
The ports below must be open on the servers where you install the cluster.
|
NOTE
For ADS, each port refers to a server on which a specific service is installed.
|
| Service | Port | Purpose |
|---|---|---|
Common |
22 |
Port for connection to SSH provider |
2015 |
TCP port to send metrics to the monitoring server |
|
2016 |
UDP port to send metrics to the monitoring server |
|
ZooKeeper |
2181 |
Service access port |
2888 3888 |
Server-to-server сommunication ports for quorum components |
|
Kafka |
9092 |
Service access HTTP port |
9093 |
Service access HTTPS port |
|
9999 |
JMX port to access service metrics |
|
Kafka-Manager |
9898 |
Service access port |
Kafka REST Proxy |
8082 |
Service access port |
9998 |
JMX-port to access service metrics |
|
Schema-Registry |
8081 |
Service access port |
9997 |
JMX-port to access service metrics |
|
ksqlDB |
8088 |
Access port to the ksqlDB Server component |
NiFi |
9090 |
Service UI access HTTP port |
9091 |
Service UI access HTTPS port |
|
11443 |
Communication port between NiFi servers clustered |
|
18080 |
Access port to the NiFi-Registry component |
| Port | Purpose |
|---|---|
3000 |
TCP port used by Grafana. The default value can be changed when installing the monitoring cluster on the configuration page of the Grafana service in the ip_and_ports section |
80 |
TCP port used by Graphite. The default value can be changed 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 |
All usable ports for an ADPS cluster are listed in Network requirements.