Skip to end of metadata
Go to start of metadata

ClustrixDB requires a number of ports to allow internode communication. Depending on your specific deployment platform, you can:

  1. Open your security to allow all communication between nodes (recommended)
  2. Open the specific ports required for your cluster. 

Ports required by ClustrixDB

This page summarizes the list of ports used by ClustrixDB. If using network security such as firewalls or security groups, the following network traffic must be allowed.

Internal Access Between ClustrixDB Nodes

These network ports are required for communication between ClustrixDB nodes. They must each be accessible by other nodes within the cluster.

ProtocolPortUseReason
TCP22SSHAdministration and upgrade
TCP, UDP2048Control PortClustrixDB specialized administrative tool
TCP, UDP2424 Nanny Portnanny - ClustrixDB process manager
TCP3306SQL

Database communication

TCP7888clxdbiDatabase interface for ClustrixGUI
TCP, UDP24378 - 24410MultiportClustrixDB internode communication

External Access

These network ports are used to access ClustrixDB externally from your applications and for cluster administration.

ProtocolPort                UseReason
TCP22SSHRemote management and cluster access   
TCP8080*HTTPClustrixGUI
TCP3306SQLDatabase access
TCP3581Health CheckHeartbeat monitor for cluster

*For root installation, ClustrixGUI uses port 80.

If you are using a firewall (like iptables) between the nodes, please open the specific ports. 

Multiport

The multiport feature allows internode communication to and from any core of a cluster. It can improve performance under heavy load.

Starting at port 24379, (for both TCP and UDP), open the same number of ports as there are cores or hyper-threads licensed for a node. The maximum number of licensed cores per node is 32, hence the suggested maximum range of 24379 - 24410.

ClustrixDB does not support mixed-mode usage of multiport. That is, all nodes must uniformly have multiport enabled (default) or disabled, or the nodes will be unable to form a cluster. 

See Modifying Startup Configuration Options for instructions on how to disable multiport, if necessary.


  • No labels