Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
To configure a production-like Redis Cluster on Ubuntu, run six Redis instances on ports 7000 through 7005, configure every instance for cluster mode and persistence, then bootstrap the group with three masters and one replica per master. Redis requires at least three masters for a cluster that works as expected; six nodes provide the commonly recommended three-master, three-replica layout.
Each instance needs a unique client port, a writable data directory, a generated cluster configuration file, a node timeout, and network access to both the client port and the cluster bus. After startup, create the cluster with redis-cli --cluster create, verify that all 16,384 hash slots are covered, and use a cluster-aware client such as redis-cli -c so redirections are followed automatically.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What a Redis Cluster on Ubuntu provides
Redis Cluster shards keys across 16,384 hash slots. Master nodes own those slots and serve reads and writes; replicas maintain copies of masters and can be promoted if a master fails. A client can connect to any reachable node, but the node may redirect the client to the master that owns the requested key.
The smallest topology that Redis describes as working as expected has three master nodes. For a deployment rather than a short-lived experiment, Redis recommends six nodes: three masters and three replicas. Place each replica in a different host, rack, availability zone, or other failure domain from its master whenever your infrastructure allows it. The exact placement depends on your Ubuntu hosts and failure model.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
| Topology | Nodes | Use |
|---|---|---|
| Minimum functional cluster | 3 masters | Distributes all 16,384 slots without replica redundancy |
| Recommended deployment shape | 3 masters and 3 replicas | One replica for each master, allowing failover testing and better availability |
| Local experiment | Multiple Redis processes on one Ubuntu host | Learning and testing only; a single host remains one failure domain |
Plan the Ubuntu deployment before installing
Choose the operating model
A manually managed deployment gives you direct control over configuration files, package versions, service supervision, firewall rules, and maintenance windows. It is appropriate when your team already operates Ubuntu services and has a standard for backups, secrets, monitoring, and upgrades.
Canonical’s Ubuntu tutorial also presents Juju as an orchestration path for AWS, Google Cloud, Azure, and bare metal. Juju can create a model, deploy Redis, configure authentication, and provide a test workflow. Compare the two approaches on host and failure-domain placement, package lifecycle, network automation, secret handling, persistence and backup integration, scaling procedures, and observability before choosing one.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Decide where nodes and addresses live
- Use six Redis instances for the recommended three-master, three-replica layout.
- Give every instance a stable address and a unique client port.
- Advertise addresses that other nodes and clients can actually reach. Do not use
127.0.0.1for a multi-host cluster; loopback addresses are suitable only for a cluster whose processes all run on the same host. - Keep data, persistence files, and the generated cluster configuration on durable storage included in your recovery plan.
- Reserve capacity for replicas, resharding, failover, and maintenance. A cluster with no spare capacity can remain technically healthy while becoming difficult to operate.
Install Redis and the command-line tools
Install the Redis server and CLI packages from the package source appropriate for your Ubuntu release. Package versions and service-unit names vary by release, so verify them rather than copying a unit name from another Ubuntu version. On releases where the standard package names are available, the typical starting point is:
sudo apt update
sudo apt install redis-server redis-tools
redis-server --version
redis-cli --versionFor a production deployment, pin or otherwise control the package version according to your organization’s change policy. The cluster procedure is independent of whether you supervise processes with systemd, another service manager, or an orchestration system, provided every instance starts reliably and can write its configured files.
Allocate ports and firewall rules
Redis uses a client port for commands and a separate cluster-bus port for node-to-node gossip, failure detection, and cluster metadata. If you do not set cluster-port, the bus defaults to the client port plus 10,000. Thus, client port 6379 uses bus port 16379, and client port 7000 normally uses bus port 17000.
| Client port | Default cluster-bus port | Typical traffic allowed |
|---|---|---|
| 6379 | 16379 | Clients to Redis; bus traffic between all members |
| 7000 | 17000 | Clients to the instance; bus traffic between all members |
| 7001 | 17001 | Clients to the instance; bus traffic between all members |
| 7002 | 17002 | Clients to the instance; bus traffic between all members |
| 7003 | 17003 | Clients to the instance; bus traffic between all members |
| 7004 | 17004 | Clients to the instance; bus traffic between all members |
| 7005 | 17005 | Clients to the instance; bus traffic between all members |
The six-row mapping above follows the default-port formula. If you explicitly configure cluster-port, open that value instead. Permit client ports only from application, administration, or monitoring networks that need them. Permit each cluster-bus port between every cluster member; allowing the client port alone is not sufficient.
Recommended Free Tools
For Ubuntu’s uncomplicated firewall, add rules matching your chosen ports and source networks. For example, a host running port 7000 might use rules shaped like:
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
sudo ufw allow from 10.0.0.0/16 to any port 7000 proto tcp
sudo ufw allow from 10.0.0.0/16 to any port 17000 proto tcpReplace the example network with the addresses of your applications and Redis nodes. Do not expose the bus to the public internet.
Create one configuration and data directory per instance
Each Redis process needs its own port, working directory, persistence files, log destination, and generated cluster configuration. Separate directories prevent six processes from overwriting each other’s files. A common layout is one directory below a parent such as /var/lib/redis-cluster/7000 through /var/lib/redis-cluster/7005, with permissions allowing the Redis service account to read and write them.
Use a configuration file like this for the instance on port 7000:
port 7000
cluster-enabled yes
cluster-config-file nodes.conf
cluster-node-timeout 5000
appendonly yesCopy the file for each instance and change port to 7001, 7002, 7003, 7004, or 7005. Set the working directory and log path to that instance’s directories using the conventions of your service manager. The cluster-config-file is generated and maintained by Redis; do not hand-edit it. Because each process has a different working directory, the same filename, nodes.conf, remains separate for each node.
Why each setting matters
cluster-enabled yesturns on cluster behavior instead of standalone Redis mode.cluster-config-file nodes.confgives Redis a place to persist node IDs, slot ownership, and cluster membership. Redis updates this file while running.cluster-node-timeout 5000sets a 5,000-millisecond failure-detection timeout in this example. Choose a value that matches your network latency and availability objectives; changing it alters how quickly failures are declared.appendonly yesenables append-only persistence. Keep the resulting files on durable storage and include them in backup and recovery planning.- A unique
portis mandatory when several instances share a host. On separate hosts, ports still need to be unique per host address and consistently advertised to clients and peers.
Start all instances before bootstrapping
Start each process with its corresponding configuration under your chosen service supervisor. A direct test launch looks like:
redis-server /etc/redis/cluster/redis-7000.conf
redis-server /etc/redis/cluster/redis-7001.conf
redis-server /etc/redis/cluster/redis-7002.conf
redis-server /etc/redis/cluster/redis-7003.conf
redis-server /etc/redis/cluster/redis-7004.conf
redis-server /etc/redis/cluster/redis-7005.confFor a real deployment, run them as supervised services rather than foreground terminals. Confirm that every process is listening on its intended client port, can write its data directory, and can reach the other nodes’ client and bus ports before running the cluster creation command.
Bootstrap the cluster with redis-cli
With six empty instances listening on ports 7000 through 7005, run the cluster creation command from a host that can reach all six addresses:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesRank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
redis-cli --cluster create
127.0.0.1:7000 127.0.0.1:7001 127.0.0.1:7002
127.0.0.1:7003 127.0.0.1:7004 127.0.0.1:7005
--cluster-replicas 1Use the real, reachable addresses in a multi-host deployment instead of the loopback addresses shown in this local example. The option --cluster-replicas 1 requests one replica for every master created. Review the proposed master and replica allocation, then answer yes when it matches your plan.
A successful bootstrap ends with:
[OK] All 16384 slots coveredThis message means every hash slot has a serving master. It does not by itself prove that your failure domains, backups, authentication, monitoring, or firewall policy are correct; those require separate checks.
Lab-only shortcut: create-cluster
Redis publishes a utils/create-cluster helper for testing and experimentation. Its documented flow is:
./create-cluster start
./create-cluster create
./create-cluster stop
./create-cluster cleanThe helper is useful for quickly creating local processes, but it is not a substitute for explicit service supervision, durable paths, controlled permissions, firewall rules, and an operational backup plan.
Connect correctly and understand MOVED errors
A plain connection to one node talks to that shard only. If the key you request belongs to another shard, Redis returns a MOVED response containing the slot and the node that owns it. This is normal cluster behavior, not evidence that the key is missing.
Use cluster-aware CLI mode:
redis-cli -c -p 7000The -c option makes redis-cli follow redirections. Application code must use a Redis Cluster-capable library that discovers the cluster topology and handles redirects. A standalone Redis client may connect successfully yet fail when it sends a command for a key owned by another master.
Validate membership, slots, and reachability
Run these checks against a reachable node after creation:
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
redis-cli -p 7000 cluster info
redis-cli -p 7000 cluster nodes
redis-cli --cluster check 127.0.0.1:7000cluster inforeports the node’s view of cluster state, including whether the cluster is able to serve.cluster nodeslists node IDs, addresses, roles, flags, and slot assignments. Confirm that you see three masters and three replicas in the recommended topology.redis-cli --cluster checkperforms a cluster-aware consistency check starting from the supplied node. Replace the loopback address with a reachable cluster address when necessary.
Diagnostic wording and fields can vary by Redis version. If a command works from the local host but fails remotely, test DNS or advertised addresses, routing, security groups, UFW rules, and both port classes separately.
Authentication and secret handling
If you enable password authentication or ACLs, apply a consistent policy to every node and configure every cluster-aware client with the required credentials. A client that can authenticate to one node but not another will appear intermittently broken as requests are redirected.
Keep credentials out of shell history, world-readable configuration files, and source control. The exact password and ACL design should follow your organization’s security standard; there is no single policy implied by the cluster bootstrap command. Test authentication against each master and replica endpoint before placing application traffic on the cluster.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Scale and maintain the cluster safely
Add capacity with a new shard
Prepare the new Redis instance with cluster mode, persistence, a unique client port, a generated configuration path, and reachable client and bus ports. Add it to the existing cluster with the cluster-aware CLI workflow, for example:
redis-cli --cluster add-node new-host:7006 existing-host:7000Adding a node does not automatically move existing hash slots to it. Treat the new node as an unassigned master until you deliberately allocate slots or assign it as a replica.
Reshard slots
Use the reshard workflow from a reachable cluster node:
redis-cli --cluster reshard existing-host:7000Review the number of slots to move, the destination master, and the source masters. Reshard during a maintenance window appropriate for your workload, monitor latency and memory, and ensure the destination has enough disk and memory for the incoming data. Moving slots changes where keys live; clients must remain cluster-aware throughout the operation.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Test and perform failover
Redis documents both failover testing and manual failover. Test by stopping or isolating a master in a controlled window and observing whether its replica is promoted and whether clients reconnect. A manual failover is an operational action, not a substitute for testing the automatic path. Record which node became master, verify slot ownership, and restore the failed node only after checking its generated cluster configuration and persistence files.
Remove or migrate nodes
Before removing a master, migrate its slots to other masters. Before removing a replica, confirm that the remaining replicas still provide the redundancy you require. The cluster CLI includes add-node and delete-node workflows, but the safe sequence is always: inspect membership, move or reassign slots, verify coverage, then remove the node and its service.
Upgrade nodes
Upgrade one node at a time with a rollback plan, backups, and a maintenance window. Keep enough healthy masters and replicas online to maintain slot coverage while a node is restarted. After each upgrade, run cluster info, cluster nodes, and redis-cli --cluster check, then test an application operation through a cluster-aware client.
Troubleshoot common setup failures
The creation command does not reach every node
Check that each address is advertised correctly and that the client port is open from the bootstrap host. Then check the cluster-bus port between every pair of members. A firewall rule for port 7000 does not open port 17000, and a rule that permits client traffic from an application subnet may still block node-to-node traffic.
The cluster reports uncovered slots
Do not send application traffic until all 16,384 slots are assigned to masters. Inspect cluster nodes and rerun the cluster check. Common causes are an interrupted bootstrap, a node started with stale cluster metadata, or a node that was unreachable during creation. Stop the affected test instances, remove only the generated cluster metadata when you are intentionally rebuilding an empty lab cluster, and recreate the cluster; never delete production metadata or persistence files without a documented recovery decision.
Clients return MOVED repeatedly
Use redis-cli -c or a Redis Cluster client library. A standalone client will keep receiving redirects because it does not maintain the slot map. If a cluster-aware client still loops, verify that the advertised node addresses are reachable from the application network and that authentication is valid on every node.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →A node keeps failing or is marked unreachable
Check process logs, disk permissions, available space, system time, routing, DNS, UFW, security groups, and both port classes. The 5,000-millisecond timeout in the example is not a universal value: a congested or high-latency network may need a different setting, while an overly long timeout delays failure detection.
Restarted nodes lose their identity
Ensure that the directory containing nodes.conf is writable and persistent, and that the service starts with the same working directory. Redis generates and maintains this file; replacing it casually can make a restarted process appear to be a new cluster member. Preserve it together with append-only data during backups and restores.
Operational checklist
- Three masters exist at minimum; the recommended deployment has three masters and three replicas.
- Every instance has a unique client port and a generated, writable cluster configuration file.
cluster-enabled yes, a deliberate node timeout, and persistence are present in every configuration.- All 16,384 slots are covered and the cluster reports a healthy serving state.
- Applications use cluster-aware clients and can reach every advertised node address.
- Firewalls permit client traffic where required and cluster-bus traffic between all members.
- Replicas occupy separate failure domains when possible.
- Backups include append-only data and generated cluster metadata, with restoration tested.
- Resharding, failover, node removal, and upgrades have written procedures and maintenance windows.
Final deployment decision
For a hands-on Ubuntu installation, explicit per-instance configuration and service supervision provide the clearest control: six nodes on ports 7000–7005, three masters, three replicas, persistent storage, and tightly scoped client and bus firewall rules. Juju is a reasonable alternative when your team wants cloud or bare-metal orchestration across supported providers. Whichever path you choose, the correctness checks are the same: reachable advertised addresses, complete slot coverage, working replicas, cluster-aware clients, and a tested recovery process.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
