Skill

Configure and Manage Redis Clusters

A Redis Cluster expert skill for production configuration, HA topology, performance tuning, and troubleshooting across multiple nodes.

Works with redisdocker

73
Spark score
out of 100
Updated 21 days ago
Version 1.0.0
Models

Add to Favorites

Why it matters

Deploy, configure, and manage production-ready Redis clusters. Ensure high availability, optimize performance, and troubleshoot issues for scalable data sharding and replication.

Outcomes

What it gets done

01

Set up Redis Cluster configurations with optimal sharding and replication.

02

Implement performance tuning for memory, connections, and persistence.

03

Automate cluster initialization, node management, and resharding.

04

Troubleshoot cluster state, split-brain scenarios, and slot migrations.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-redis-cluster-config | bash

Overview

Redis Cluster Configuration Expert

This skill covers Redis Cluster configuration and operations: sharding architecture, redis.conf and Docker Compose setups, cluster creation and node management, HA practices, performance tuning, and troubleshooting for split-brain and slot-migration issues. Use it when configuring, scaling, or troubleshooting a multi-node Redis Cluster deployment. Not a substitute for environment-specific validation and expert review.

What it does

This skill provides production-ready Redis Cluster configuration, deployment, and operations guidance: architecture fundamentals covering 16384-hash-slot sharding, master-replica topology, gossip-protocol cluster state, client-side slot routing, and a minimum of three master nodes for quorum; a full redis.conf template for cluster nodes covering cluster settings, memory limits and eviction policy, persistence via RDB save intervals plus AOF, security settings like requirepass, masterauth, protected-mode, and bind, and logging; a Docker Compose setup for a three-node cluster; cluster lifecycle commands to create a cluster with replicas, verify status via cluster info and cluster nodes, add master or replica nodes, reshard slots, and remove a node after draining it. It also covers high-availability practices - replicas spread across availability zones, cluster-require-full-coverage, replica-validity-factor, and replication-lag monitoring - a bash health-check script that pings nodes and checks cluster_state, performance tuning around maxmemory-policy, memory fragmentation, hash-max-ziplist-entries, connection pooling, and tcp-keepalive, a Python RedisCluster client configuration example, troubleshooting for cluster state corruption and split-brain prevention, slot-migration monitoring and repair via --cluster fix, and security and backup guidance including TLS for inter-node traffic, Redis 6+ ACLs, password rotation, and tested RDB/AOF backup restoration.

When to use - and when NOT to

Use it when configuring, deploying, scaling, or troubleshooting a Redis Cluster deployment across multiple nodes - sharding strategy, high-availability setup, performance tuning, or diagnosing split-brain and migration issues. Do not treat its output as a substitute for environment-specific validation, testing, or expert review, and stop for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Inputs and outputs

Given a target topology - node count, availability zones, workload profile - it produces redis.conf templates, Docker Compose manifests, redis-cli cluster commands for creation, scaling, and repair, client configuration snippets, and health-check or troubleshooting scripts.

Integrations

redis-cli --cluster create 10.0.1.10:6379 10.0.1.11:6379 10.0.1.12:6379 10.0.1.13:6379 10.0.1.14:6379 10.0.1.15:6379 --cluster-replicas 1

Works with redis-cli's cluster subcommands, Docker Compose for local multi-node testing, and language clients such as Python's RedisCluster; it also recommends network-level integrations like VPC or security groups and TLS for inter-node traffic in sensitive environments.

Who it's for

Infrastructure and backend engineers deploying or operating Redis Cluster at scale who need concrete configs, high-availability topology guidance, and a troubleshooting playbook for slot migration, split-brain, and cluster-state issues, rather than generic single-node Redis advice. It also connects the Python client configuration - startup nodes, decode_responses, socket timeouts and keepalive, and a max_connections pool size - to the operational side, so client behavior stays consistent with how the cluster itself is tuned for timeouts and connection handling.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.