Skip to content

FIX #651 try next Sentinel node on TimeoutError #684

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

Merged
merged 1 commit into from
Nov 27, 2015

Conversation

blopker
Copy link
Contributor

@blopker blopker commented Nov 27, 2015

A failure we are seeing in production is that Sentinel nodes are timing out instead of just throwing ConnectionErrors. This keeps the clients from getting the new master and brings down the app.

Same PR as #652, but with tests.

@andymccurdy
Copy link
Contributor

Thanks!

andymccurdy added a commit that referenced this pull request Nov 27, 2015
FIX #651 try next Sentinel node on TimeoutError
@andymccurdy andymccurdy merged commit da13784 into redis:master Nov 27, 2015
@blopker blopker deleted the feature/sentinel-timeout branch November 28, 2015 23:58
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.

2 participants