Before deploying Redis, review and complete the Core Hardware & OS Setup, configure your Network Configuration, and apply key Operating System Optimization. Plan your Cluster Sizing & Topology to meet quorum and enable rack-zone awareness for high availability.
Lastly, check for any Environment-Specific Considerations.
When ready, complete the final step of sharing with Redis Support to validate your deployment.
Core Hardware & OS Setup
Your equipment should meet the basic hardware requirements, and should also have extra capabilities depending on the amount of data, volume of traffic, and number of databases.
These are starting points. Scale up as needed:
Minimum Requirements:
- CPU: 4 cores per node (Minimum: 2 cores per node, Recommended: >=8 cores)
- RAM: 15 GB per node (Minimum: 8 GB, Recommended: >=32 GB)
CPU Sizing Guidelines
- 1 shard per ~25,000 ops/sec
- 1.5 CPUs per shard (per primary and each replica)
- Additional 0.5 CPU per shard for DMC proxy overhead
- Leave ~20% CPU per node for non-database processes
RAM Sizing Guidelines
- 1 shard per ~25 GiB RAM
- Leave ~20% RAM unused by non-database storage
Choose the Supported Operating System (OS): Redis supports various Linux distributions, including RHEL, CentOS, and Ubuntu. Make sure your OS is up-to-date and compatible. For more information, please visit Plan Deployment
Network Configuration
Select Low Latency & High-Throughput Network:
For best performance, use multiple NICs per node with >100 Mbps each.
Alternatively, a single 1 Gbps NIC can support traffic, cluster communication, and storage access. Choose based on your infrastructure and workload needs.
Open Required Network Ports:
Redis requires specific ports to be open for node-to-node communication.
The installation process will fail if the designated ports, specifically those assigned for databases or port 53 on Ubuntu, are already in use.
Refer to the For more information, please visit Port Configurations.
Operating System Optimization
Disable Linux Swap: Turn off swap space to prevent performance degradation.
Follow the instructions in Configure Swap for Linux for a step-by-step guide.
Synchronize Cluster Node Clocks: To maintain accurate time synchronization among nodes in a cluster, it's essential to use NTP or Chrony.
See more information in Synchronize Cluster Node Clocks
Cluster Sizing & Topology
Decide on Number of Nodes: A Redis cluster requires a minimum of 3 nodes (always an odd number) to maintain quorum and ensure high availability. This allows the cluster to tolerate failures while preserving consistency. Clusters with more than 35 nodes aren't supported.
Enable Rack-Zone Awareness: Distribute nodes across different racks or zones to improve fault tolerance and ensure high availability. For more information, please visit Rack-zone Awareness.
Next Step: Share with Redis Support
After configuring your infrastructure, it's recommended to upload a support package for the Redis team to review. This allows them to provide feedback and ensure your deployment aligns with best practices.
Onboarding Progress
Previous: Introduction to Redis Software
Next: Installing Redis Software
Return to the Redis Software Onboarding Overview to view all steps.
0 comments
Please sign in to leave a comment.