Core exceptions raised by the Redis client
- exception redis.exceptions.AskError(resp)¶
Error indicated ASK error received from cluster. When a slot is set as MIGRATING, the node will accept all queries that pertain to this hash slot, but only if the key in question exists, otherwise the query is forwarded using a -ASK redirection to the node that is target of the migration. src node: MIGRATING to dst node
get > ASK error ask dst node > ASKING command
- dst node: IMPORTING from src node
asking command only affects next command any op will be allowed after asking command
- exception redis.exceptions.AuthenticationError¶
- exception redis.exceptions.AuthenticationWrongNumberOfArgsError¶
An error to indicate that the wrong number of args were sent to the AUTH command
- exception redis.exceptions.AuthorizationError¶
- exception redis.exceptions.BusyLoadingError¶
- exception redis.exceptions.ChildDeadlockedError¶
Error indicating that a child process is deadlocked after a fork()
- exception redis.exceptions.ClusterCrossSlotError¶
Error indicated CROSSSLOT error received from cluster. A CROSSSLOT error is generated when keys in a request don’t hash to the same slot.
- exception redis.exceptions.ClusterDownError(resp)¶
Error indicated CLUSTERDOWN error received from cluster. By default Redis Cluster nodes stop accepting queries if they detect there is at least a hash slot uncovered (no available node is serving it). This way if the cluster is partially down (for example a range of hash slots are no longer covered) the entire cluster eventually becomes unavailable. It automatically returns available as soon as all the slots are covered again.
- exception redis.exceptions.ClusterError¶
Cluster errors occurred multiple times, resulting in an exhaustion of the command execution TTL
- exception redis.exceptions.ConnectionError¶
- exception redis.exceptions.DataError¶
- exception redis.exceptions.ExecAbortError¶
- exception redis.exceptions.InvalidResponse¶
- exception redis.exceptions.LockError¶
Errors acquiring or releasing a lock
- exception redis.exceptions.LockNotOwnedError¶
Error trying to extend or release a lock that is (no longer) owned
- exception redis.exceptions.MasterDownError(resp)¶
Error indicated MASTERDOWN error received from cluster. Link with MASTER is down and replica-serve-stale-data is set to ‘no’.
- exception redis.exceptions.MaxConnectionsError¶
- exception redis.exceptions.ModuleError¶
- exception redis.exceptions.MovedError(resp)¶
Error indicated MOVED error received from cluster. A request sent to a node that doesn’t serve this key will be replayed with a MOVED error that points to the correct node.
- exception redis.exceptions.NoPermissionError¶
- exception redis.exceptions.NoScriptError¶
- exception redis.exceptions.PubSubError¶
- exception redis.exceptions.ReadOnlyError¶
- exception redis.exceptions.RedisClusterException¶
Base exception for the RedisCluster client
- exception redis.exceptions.RedisError¶
- exception redis.exceptions.ResponseError¶
- exception redis.exceptions.SlotNotCoveredError¶
This error only happens in the case where the connection pool will try to fetch what node that is covered by a given slot.
If this error is raised the client should drop the current node layout and attempt to reconnect and refresh the node layout again
- exception redis.exceptions.TimeoutError¶
- exception redis.exceptions.TryAgainError(*args, **kwargs)¶
Error indicated TRYAGAIN error received from cluster. Operations on keys that don’t exist or are - during resharding - split between the source and destination nodes, will generate a -TRYAGAIN error.
- exception redis.exceptions.WatchError¶