Documentation - Redise Pack

A guide to Redise Pack installation, operation and administration

open all | close all

Private and Public Endpoints

The cluster can now be configured to support both private and public IPs to connect to database endpoints through both public and private networks.

In certain environments, and especially in cloud platforms, an instance can have both:

  • A private IP address that can be used only from within the internal network
  • Public IP address(es) that can be used from the public network (Internet)

In this case, it is possible to configure Redise Pack to expose two sets of database endpoints in order to connect to the database through both the private and the public IP addresses.

To enable this configuration you need to:

  • The IPs must already be bound to the server/instance.
  • Enable support when the cluster is created for a new cluster or using rladmin for an existing cluster.
  • Configure public IP of the machine to be used for external traffic in the node configuration.
  • Configure private IP to be used for both internal and external traffic in the node configuration so it can be used for private database endpoints.

Once this configuration is in place, both sets of endpoints will be available for the databases in the cluster.

Modifying an Existing Cluster

Once you have have a 4.4 cluster, if you would like to take advantage of this new feature, you can enable it by using the rladmin suffix add command.

To add an internal FQDN/IP to a cluster:

$ rladmin suffix add name <node1.internal.clustername.domain.com> internal

 

To add an internal FQDN/IP to a cluster, but signal to the cluster there is slave for DNS:

$ rladmin suffix add name <node2.internal.clustername.domain.com> internal slave 10.0.1.1