Skip to content

Latest commit

 

History

History
70 lines (55 loc) · 3.32 KB

retry.rst

File metadata and controls

70 lines (55 loc) · 3.32 KB

Retry Helpers

.. automodule:: redis.retry
    :members:


Retry in Redis Standalone

>>> from redis.backoff import ExponentialBackoff
>>> from redis.retry import Retry
>>> from redis.client import Redis
>>> from redis.exceptions import (
>>>    BusyLoadingError,
>>>    ConnectionError,
>>>    TimeoutError
>>> )
>>>
>>> # Run 3 retries with exponential backoff strategy
>>> retry = Retry(ExponentialBackoff(), 3)
>>> # Redis client with retries on custom errors
>>> r = Redis(host='localhost', port=6379, retry=retry, retry_on_error=[BusyLoadingError, ConnectionError, TimeoutError])
>>> # Redis client with retries on TimeoutError only
>>> r_only_timeout = Redis(host='localhost', port=6379, retry=retry, retry_on_timeout=True)

As you can see from the example above, Redis client supports 3 parameters to configure the retry behaviour:

If either retry_on_error or retry_on_timeout are passed and no retry is given, by default it uses a Retry(NoBackoff(), 1) (meaning 1 retry right after the first failure).

Retry in Redis Cluster

>>> from redis.backoff import ExponentialBackoff
>>> from redis.retry import Retry
>>> from redis.cluster import RedisCluster
>>>
>>> # Run 3 retries with exponential backoff strategy
>>> retry = Retry(ExponentialBackoff(), 3)
>>> # Redis Cluster client with retries
>>> rc = RedisCluster(host='localhost', port=6379, retry=retry, cluster_error_retry_attempts=2)

Retry behaviour in Redis Cluster is a little bit different from Standalone:

Let's consider the following example:

>>> from redis.backoff import ExponentialBackoff
>>> from redis.retry import Retry
>>> from redis.cluster import RedisCluster
>>>
>>> rc = RedisCluster(host='localhost', port=6379, retry=Retry(ExponentialBackoff(), 6), cluster_error_retry_attempts=1)
>>> rc.set('foo', 'bar')
  1. the client library calculates the hash slot for key 'foo'.
  2. given the hash slot, it then determines which node to connect to, in order to execute the command.
  3. during the connection, a :class:`~.ConnectionError` is raised.
  4. because we set retry=Retry(ExponentialBackoff(), 6), the client tries to reconnect to the node up to 6 times, with an exponential backoff between each attempt.
  5. even after 6 retries, the client is still unable to connect.
  6. because we set cluster_error_retry_attempts=1, before giving up, the client starts a cluster update, removes the failed node from the startup nodes, and re-initializes the cluster.
  7. after the cluster has been re-initialized, it starts a new cycle of retries, up to 6 retries, with an exponential backoff.
  8. if the client can connect, we're good. Otherwise, the exception is finally raised to the caller, because we've run out of attempts.