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

Next sentinel host is not contacted after socket timeout #651

Closed
svend opened this issue Sep 2, 2015 · 0 comments
Closed

Next sentinel host is not contacted after socket timeout #651

svend opened this issue Sep 2, 2015 · 0 comments

Comments

@svend
Copy link

svend commented Sep 2, 2015

If a there is a socket timeout with a sentinel host, redis.exceptions.TimeoutError is returned and none of the other sentinel hosts are contacted.

If there is a connection timeout or connection refused, the next host is tried. It would great if there was way to try the next sentinel host in the same way for socket timeout errors.

(You can retry_on_timeout=True to retry the same sentinel host once, but if you get a socket timeout a second time, redis.exceptions.TimeoutError is returned.)

andymccurdy added a commit that referenced this issue Nov 27, 2015
FIX #651 try next Sentinel node on TimeoutError
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 a pull request may close this issue.

1 participant