database
Redis Errors
Redis errors: WRONGTYPE (operation against wrong type key), MOVED (cluster redirect), ASK (cluster slot migrating), READONLY (replica write attempt), OOM (out of memory), MAXCLIENTS REACHED.
Redis Cluster slot errors (MOVED, ASK) are normal — your client should follow them. WRONGTYPE means a key exists with a different type than expected (often a leftover from a previous version). OOM with `maxmemory-policy: noeviction` blocks all writes — pick a sensible eviction policy. CROSSSLOT errors come from multi-key commands across slots in cluster mode.
Database (2)
-
OOMOut of MemoryRedis hit its `maxmemory` limit and the configured `maxmemory-policy` is `noeviction` (the default), so it refuses every write. Reads still work; commands that allocate memory return `OOM command not allowed when used memory > 'maxmemory'`. -
WRONGTYPEWrong Key TypeYou ran a Redis command that only works on a specific data type (e.g., `LPUSH` on lists) against a key that holds a different type (e.g., a string). Each Redis key has exactly one type — set when first written — and commands are type-specific.
Official docs
https://redis.io/docs/reference/protocol-spec/#resp-errors
Support
https://redis.io/community/