Master Redis replication - master-replica setup, Sentinel for HA, failover handling, and read scaling patterns
Configures Redis master-replica replication with Sentinel for automatic failover and high availability. Use when setting up production Redis, implementing read scaling, or troubleshooting replication issues like split-brain or failed failovers.
/plugin marketplace add pluginagentmarketplace/custom-plugin-redis/plugin install pluginagentmarketplace-developer-roadmap-interactive@pluginagentmarketplace/custom-plugin-redisThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/config.yamlassets/docker-compose-ha.ymlassets/sentinel.confreferences/GUIDE.mdreferences/REPLICATION_GUIDE.mdscripts/check-replication.shscripts/helper.pyreplicaof master_ip 6379
masterauth your_password
replica-read-only yes
replica-serve-stale-data yes
REPLICAOF master_ip 6379 # Set master
REPLICAOF NO ONE # Promote to master
INFO replication # Check status
Sentinel 1 Sentinel 2 Sentinel 3
↓ ↓ ↓
└──────── Monitor ───────────┘
↓
Master ←──→ Replica 1 ←──→ Replica 2
# sentinel.conf
port 26379
sentinel monitor mymaster 192.168.1.10 6379 2
sentinel auth-pass mymaster password
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 60000
sentinel parallel-syncs mymaster 1
# On Sentinel port
SENTINEL masters
SENTINEL get-master-addr-by-name mymaster
SENTINEL failover mymaster
SENTINEL replicas mymaster
INFO replication
# role:master|slave
# connected_slaves:2
# slave0:ip=...,port=...,state=online,offset=...,lag=0
sentinel.conf - Sentinel configurationdocker-compose-ha.yml - HA Docker setupREPLICATION_GUIDE.md - Setup guideINFO replication # Check master_link_status
Fix: Check network, password, and firewall
min-replicas-to-write 1
min-replicas-max-lag 10
Check: Quorum (need majority of Sentinels)
| Code | Name | Recovery |
|---|---|---|
| R001 | MASTERDOWN | Check master or failover |
| R002 | SYNC_FAILED | Check network/auth |
| R003 | QUORUM_LOST | Restore Sentinel majority |
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.