You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 733f80e
Browse filesBrowse the repository at this point in the historyBrowse files
Updates in default connection and retry settings (#4082)
* Updating default socket keep alive config
* Updating default socket read size to 32 kb
* Updating default socket_timeout and socket_connect_timeout values to 5s
* Updating the default retry configuration
* Updating max_connections allowed in ConnectionPool
* Unifying SENTINEL marker usage throughout library method args
* Fixing failing maint notifications tests - updated the expected original timeout to be 5s
* Fixing backing up socket_timeout and socket_connect_timeout for maint notifications handling
* Fixing linters
* Fixing failing tests - after changing default retry counts for cluster and max_connections in pool some test configs needed to be updated
* Fixing linters
* Fixing failing tests
* Using socket timeout constants for all default socket timeout configs
* Applying review comments
* Fixing linters
* Extracting retry count,base and cap configs as constants
Copy file name to clipboardExpand all lines: docs/retry.rst
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,8 +48,8 @@ Retry in Redis Cluster
48
48
49
49
Retry behaviour in Redis Cluster is a little bit different from Standalone:
50
50
51
-
* ``retry``: :class:`~.Retry` instance with a :ref:`backoff-label` strategy and the max number of retries, default value is ``Retry(ExponentialWithJitterBackoff(base=1, cap=10), cluster_error_retry_attempts)``
52
-
* ``cluster_error_retry_attempts``: number of times to retry before raising an error when :class:`~.TimeoutError`, :class:`~.ConnectionError`, :class:`~.ClusterDownError` or :class:`~.SlotNotCoveredError` are encountered, default value is ``3``
51
+
* ``retry``: :class:`~.Retry` instance with a :ref:`backoff-label` strategy and the max number of retries, default value is ``Retry(ExponentialWithJitterBackoff(base=0.01, cap=1), cluster_error_retry_attempts)``
52
+
* ``cluster_error_retry_attempts``: number of times to retry before raising an error when :class:`~.TimeoutError`, :class:`~.ConnectionError`, :class:`~.ClusterDownError` or :class:`~.SlotNotCoveredError` are encountered, default value is ``10``
53
53
* This argument is deprecated - it is used to initialize the number of retries for the retry object,
54
54
only in the case when the ``retry`` object is not provided.
55
55
When the ``retry`` argument is provided, the ``cluster_error_retry_attempts`` argument is ignored!
@@ -70,4 +70,4 @@ Let's consider the following example:
70
70
#. given the hash slot, it then determines which node to connect to, in order to execute the command.
71
71
#. during the connection, a :class:`~.ConnectionError` is raised.
72
72
#. because we set ``retry=Retry(ExponentialBackoff(), 6)``, the cluster client starts a cluster update, removes the failed node from the startup nodes, and re-initializes the cluster.
73
-
#. the cluster client retries the command until it either succeeds or the max number of retries is reached.
73
+
#. the cluster client retries the command until it either succeeds or the max number of retries is reached.
0 commit comments