redis
Redis Sentinel master discovery failure
ERR.*sentinel.*master.*not found|Sentinel.*failover.*error
Fixes
- 1.Verify sentinel nodes are running and can reach the Redis master
- 2.Check master name in client config matches sentinel's monitored master name
- 3.Ensure at least quorum number of sentinels agree on master location
redissentinelfailover
Related Errors
redis3 fixes
Redis operation on wrong data type
Redis.*WRONGTYPE Operation against a key holding the wrong kind of value
- •Check key type with TYPE command before operating
- •Delete and recreate key if type needs to change
redis3 fixes
Redis cluster is down
Redis.*CLUSTERDOWN.*The cluster is down
- •Check cluster health: redis-cli --cluster check <host>:<port>
- •Verify all master nodes have sufficient slots assigned
redis3 fixes
Redis cluster CROSSSLOT error
Redis.*ERR Error running script.*CROSSSLOT Keys in request don't hash to the same slot
- •Use hash tags to force keys to same slot: {user:1}:profile, {user:1}:settings
- •Split multi-key operation into per-slot operations