redis
Redis EVALSHA script not in cache
NOSCRIPT.*No matching script|EVALSHA.*script not cached
Fixes
- 1.Fall back to EVAL with full script when EVALSHA returns NOSCRIPT
- 2.Use SCRIPT LOAD on application startup to pre-cache scripts
- 3.After Redis restart, scripts must be reloaded — implement automatic reload logic
redisluaevalsha
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