Installing and Upgrading
This section explains how to install, upgrade and uninstall Redis Enterprise Software (RS).
The first thing you need to decide is how you will deploy Redis Enterprise Software. If on-premise or in the cloud and you want to install it yourself, you will need to download the package. If on docker or through an AMI, there are other instructions than this page for that. Regardless, navigate to the Redis Labs download page and select one of the following options: Installation package - Click the Download button for the OS you would like to use in order to download the .
There are some special considerations that are important when installing and running Redis Enterprise Software (RS) on an AWS instances. Storage Considerations AWS instances are ephemeral, but your persistent database storage should not be. If you require a persistent storage location for your database, the storage must be located outside of the instance. Therefore, when you set up an instance make sure that it has a properly sized EBS backed volume connected.
Below is a table of which directories Redis Enterprise Software (RS) installs into and/or utilizes. Path Description /opt/redislabs This is the main installation directory for all Redis Enterprise Software binaries /opt/redislabs/bin Binaries for all the utilities for command line access and managements such as "rladmin" or "redis-cli" /opt/redislabs/config System configuration files /opt/redislabs/lib System library files /opt/redislabs/sbin System binaries for tweaking provisioning /var/opt/redislabs Default storage location for the cluster data, system logs, backups and ephemeral, persisted data /var/opt/redislabs/log System logs for Redis Enterprise Software /etc/opt/redislabs Default location for cluster manager configuration and certificates /tmp Temporary files Note: At this time, changing the directories RS installs to is not supported.
By default, the installation process requires an Internet connection to enable installing dependency packages and for synchronizing the operating system clock against an NTP server (for additional details, refer to Synchronizing node clocks. If you install Redis Enterprise Software (RS) on a machine with no Internet connection, you need to perform these two tasks manually, as follows: First, you need to install the required dependency packages. When RS is installed on a machine that is not connected to the Internet, the installation process fails and displays an error message informing you it failed to automatically install dependencies.
To complete the upgrade process you must upgrade the Redis Enterprise Software (RS) software on each of the nodes and then upgrade each of the databases in the cluster. Warning - Before you upgrade, you must read the RS 5.4 release notes, including the 5.4 upgrade notes. Version requirements: To upgrade your cluster to v5.4, your cluster must first be on 5.0 or above To upgrade your cluster to v5.
In the event that you need to uninstall Redis Enterprise Software (RS) from a server, please run the following command in the operating system CLI: In Ubuntu: $ sudo apt-get purge redislabs In CentOS / RHEL: $ sudo yum remove redislabs After you confirm the uninstallation, the uninstall process runs and removes the RS installation from the server. Note: If you would like to uninstall RS, but keep the configuration and persistence files intact, then you can use the apt-get remove command in Ubuntu, or the rpm -e command in RHEL/CentOS/OEL.
This section details many aspects of the OS and Redis Enterprise Software configurations necessary. CentOS / RHEL 7 firewall configuration CentOS / RHEL7 distributions have, by default, a restrictive firewall mechanism based on firewalld (which in turn configures the standard iptables system). The default configuration assigns the network interfaces to the public zone and blocks all ports, except 22 (SSH). Redis Enterprise Software (RS) installation on CentOS / RHEL 7 automatically creates two firewalld system services: A service named redislabs, which includes all ports and protocols needed for communications between cluster nodes.