Documentation - Redise Pack

A guide to Redise Pack installation, operation and administration

open all | close all

Network port configuration

Servers used as Redise Pack (RP) nodes should ideally have all the below ports open between them for internal cluster communication purposes.

In addition, ensure that the ICMP protocol is enabled for communications between the nodes.

By default, the cluster assigns ports in the range of 10,000 – 19,999 to database endpoints. If you assign a specific port for a database when creating it, even outside of this range, the cluster will only verify that the assigned port is not already in use. You will have to manually update your firewall with the port for that new database endpoint.

List of ports and port ranges used by Redise Pack

Port Description Protocol
3333, 3334, 3335, 3336, 3337, 36379, 36380 Internal cluster usage  TCP
53 Used for accessing DNS/mDNS functionality in the cluster  TCP, UDP
5353 Used for accessing DNS/mDNS functionality in the cluster  UDP
8001 Used by your application to access the RP Discovery Service  TCP
8443 Used for secure (https) access to the management web UI  TCP
8444, 9080 Used for nginx <->cnm_http/cm communications on the same host only. Ports are bound to loopback adapter.  TCP
8080, 9443 Used to expose the REST API for cluster management  TCP
10000-19999 Used for exposing databases externally  TCP
20000-29999 Used for internal communications with database shards  TCP

Changing the Management Web UI Port

You may change the port used for the RP Web UI. To do that, run the following command on any node in the cluster as this is a cluster wide setting:

$ rladmin cluster config cm_port <new-port>

Note: Make sure to check the new port is not already in use by some other process before running this command.