Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow configuration of cluster retry wait duration #859

Merged
merged 2 commits into from
Jun 28, 2023

Conversation

nihohit
Copy link
Contributor

@nihohit nihohit commented Jun 6, 2023

This change allows the user to configure the wait duration between retry
attempts in the cluster clients. The change doesn't the current wait time,
but it does contain a fix to the tests, which will allow us to reduce the defaults
without breaking the tests.

This change also introduces jitter, so that if multiple requests
are waiting, they won't be all sent at exactly the same time.

This change allows the user to configure the wait duration between retry
attempts in the cluster clients.

This change also introduces jitter, so that if multiple requests
are waiting, they won't be all sent at exactly the same time.
During the development of the feature I ran tests with lower wait time
between retries, and often received CLUSTERDOWN errors. This means
that RedisCluster wasn't ready to use when constructed.
@nihohit
Copy link
Contributor Author

nihohit commented Jun 27, 2023

@jaymell rebased

@jaymell jaymell merged commit 2e87480 into redis-rs:main Jun 28, 2023
8 of 9 checks passed
@nihohit nihohit deleted the configure-retries branch June 28, 2023 07:11
altanozlu pushed a commit to altanozlu/redis-rs that referenced this pull request Aug 16, 2023
* Allow configuration of cluster retry wait duration

This change allows the user to configure the wait duration between retry
attempts in the cluster clients.

This change also introduces jitter, so that if multiple requests
are waiting, they won't be all sent at exactly the same time.

* Test cluster: wait for status ok in log file.

During the development of the feature I ran tests with lower wait time
between retries, and often received CLUSTERDOWN errors. This means
that RedisCluster wasn't ready to use when constructed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants